SAP SFTP adapter firing in more than one node

[Former Member]

Hi,

Our sender comm channels using the SAP SFTP adapter are firing in more than one node.

For example we have one adapter that is set to run every sixty minutes. In comm channel monitoring I can see that in two of the four available nodes the adapter is firing at 10 minutes past the hour on one node and 20 minutes past the hour on other.

What could be causing this and what might be the solution? We are not yet applied the service pack for the SFTP adapter.

In the default java logs I see the following error being logged every minute. Could this be related?

I am not a java administrator.

Message:	Cannot access inbound channel configuration. Received exception: null
Date:	2013-05-22
Time:	12:33:15:951
Category:	com.sap.aii.adapter.sftp.ra.rar.jca.SPIManagedConnectionFactory
Location:	com.sap.aii.adapter.sftp.ra.rar.jca.SPIManagedConnectionFactory.run()
Application:
Thread:	XI AF SFTP Adapter MCF 6e932db9-7b1c-11e2-a19f-0000014b7cbf
Data Source:	j2ee\cluster\server1\log\defaultTrace_01.trc
Arguments:
DSR Transaction:	5b8b9da27b1c11e281020000014b7cbf
Message Code:
Session:	0
Transaction:
User:	J2EE_GUEST
Time Zone:	+1000
CSN Component:	BC-XI-CON-B2B
DC Component:	sap.com/com.sap.aii.adapter.sftp.app
Correlation ID:	21724351000000718
DSR Root Context ID:	5B8B9DA27B1C11E281020000014B7CBF
DSR Connection:	5b8b9da27b1c11e281020000014b7cbf
DSR Counter:	0
Host:	xxxxxxxxx
System:	FPP
Instance:	xxxxxx
Node:	server1
Log ID:	00010001156D61580002387500002AA0

thanks

Julian

[marcelom_bovo]

Hello, 

I know this is a and old post, but I got into the same problem(multiple nodes getting the same file) and found the note 2424450 which address this issue

Symptom

In SFTP Adapter, the same file at the Sender channel is processed multiple times. This can be due to the following reasons.

1. The fact that the source file was not deleted after processing the first time due to some run time issues (like file locks, network faults, etc).

2. In cluster node environment where multiple server nodes try to process the same file simultaneously.

As a result, the same transaction gets executed twice, which is erroneous.

Solution

The solution involves a source code fix. At the start of processing, we validate if the file has already been processed (i.e file has been sent from the Sender Channel to the Module processor successfully). If the file has already been processed once, we skip the processing of the current file and move it to a secondary folder named "DuplicateMessageContent", which is located within the Source Directory mentioned in the Sender Channel Configuration.

To enable this new feature, the additional parameter "removeProcessedFiles" has to be set to "true".

Note: Ensure that necessary write permission is provided for the PI SFTP Adapter to create a new Directory named "DuplicateMessageContent" within the Source Directory. If sufficient permissions are not provided, it will result in a run time exception.