Sender FTP Communication Channel active and polling but not picking some files from source directory

[former_member323756]

Hello All,

The Sender File Communication Channel is configured to poll a fixed source directory at  FTP location every 400 seconds. The files to be picked are all .csv files.

The Channel is active, error-free and polling continuously but sometimes it stops picking the files all of a sudden for no visible reason.

1.Changing the Communication Channel in ID from active to inactive and reactivating it.

2.Stopping and restarting the CC in CC monitoring (RWB).

3.If Not, then Creating a similar new channel.

One or all of these sequential steps have solved the issue till date but temporarily.

But since 4 days now, every day out of 25 -40 .csv files are placed in same directory path. Channel is active and polling at fixed interval. It picks a few files and then it stops processing the rest of them. Also, the 3 steps given above are not helping.

Manual posting of files is the only way to take care of this which is a big risk as its production issue and Payment files from bank.

Also, with next day's batch of files , the previous days files are processed along with.(which have already been posted manually to avoid delay)

Could you guys provide some valuable suggestions. The threads already available do not provide any other solution that these recurring steps.

Also, please guide what could be the possible reason for this .

Regards,

Shikha Chaudhary

[engswee]

Hi Shikha

A few other things to consider:

- Are there any long running locks in NWA? An example of a thread related to NWA locks below

- Are there any queues where the worker threads are fully used?

You can check the queues at the following location

RWB -> Component Monitoring -> Adapter Engine -> Engine Status -> Additional Data

Rgds

Eng Swee

[former_member323756]

Hello ,

Thanks for the reply. Not having the necessary authorizations, I have asked the Basis team to check for NWA locks . Will keep the thread posted with the findings.

Regards,

Shikha

[azharshaikh]

Hi Shikha,

Have you configured the CC Connect Mode for - Per File Transfer or Permanently...

Pls try with Per File Transfer.

Also as per Note # 849089 can you try adding - configure a timeout for the FTP connection, please enable the "Advanced Mode" for the respective FTP communication channel in the Integration Directory and add an entry "ftp.timeout"=timeoutSecs (without any quotation marks) to the "Additional Parameters" section, where timeoutSecs is the desired FTP timeout in seconds.

There might be issue with the FTP user unable to read/process the files due to access/authorization issue for the other files. Please check.

Regards,

Azhar

[former_member323756]

Hello,

FTP user is quite able to access the files in directory as some of the files are picked and after sometime it stops picking.

Connection mode is set to Permanently. I will check this setting as well once the next batch of files is planned to be posted.

Regards,

Shikha

[Former Member]

Hello,

Could you please try to define a timeout (in secs - for instance 120) in the channel and check?

Check note #821267 - FAQ: XI 3.0 / PI 7.0/ PI 7.1 File Adapter

- point 8. FTP Adapter Timeout Configuration

thanks-
Rams

[former_member323756]

Hello Rams,

Thanks for the suggestion. I will get back to you after trying this out. I will have to wait for next file posting to test if it is working fine.

Regards,

Shikha Chaudhary

[former_member184681]

Hi Shikha Chaudhary,

What is the Communication Channel config you are using? Did you type a generic file name scheme, like *.csv? What are the file attributes, e.g. are they read-only -> this has some consequences on how PI works with a file.

Regards,

Grzegorz

[former_member323756]

Hi Grzegorz,

Thanks for the quick reply.

Yes, the file name is  *.csv and files are read only payment files.

What should be the suggested next step.

Regards,

Shikha

[former_member184681]

Dear Shikha,

Do you use Quality of Service: Exactly Once In Order for this interface, e.g. by having the "Maintain Order At Runtime" checkbox marked in Interface Determination? If so, a single error in the interface blocks processing further messages -> you have to deal with such error first, before further messages will be processed = before further files will be picked up from source directory.

Also, for read-only files, it is only possible to process them with File Adapter - see point #13 here:

Configuring the Sender File Adapter - Configuring the File/FTP Adapter in Integration Directory/PCK ...

However, FTP Adapter does not have this option, so such files cannot be processed at all, unless the read-only attribute is NOT set by the sender - see more details here:

Configuring the Sender FTP Adapter - Configuring the File/FTP Adapter in Integration Directory/PCK -...

Regards,

Grzegorz

[naveen_chichili]

Hi Shikha,

Some times empty file handling also cause the problem.

if any file with '0'bytes has arrived into your source folder some times based on your empty file handling option files might get choked.

Regards,

Naveen

[former_member323756]

Hello Grzegorz,

The Quality of Service: Exactly Once.

But "Maintain Order At Runtime" checkbox is marked in Interface Determination.

Files are read-only but they are always processed by same FTP sender channel; only sometimes such kinds of issues are faced. Hence I doubt about this constraint of FTP adapter in our issue.

Any other clue?

Regards,

Shikha Chaudhary

[former_member323756]

Hi Naveen,

I checked with the concerned team.None of the files sent was empty.

Thanks for the reply anyways.

Regards,

Shikha