File is not picked up by channel for 2 days due to time out error

[Former Member]

Hi All,

I have an issue to which I could not find the exact answer why that happens:

a file is placed in FTP folder from  where it will be picked up by the channel and will processed in PI and sent to ECC.

On 11 Oct 2013 ,  we got an issue that file is not picked up by the interface , When trying to investigate the same, I found that there was an temporary time out error for some time ( for 5 mins like that)  . and the channel was working fine after some time.

So in the period of time out , the channel has not picked up the file placed in the folder.

But when the channel is up,  all the files were picked up and processed by PI except the file which was not picked up earlier at the time out error .

After 2 days ,  the file was picked up by the channel finally .

But here,  my question is :

why the channel has not picked up the channel on the next instance of availability of channel where other messages are picked up by the channel .

What may be the problem in this:

I could not find the exact answer for this:

Please help me.

Thanks,

Venkat

[iaki_vila]

Hi Venkataro,

I think the Note 1549500 - XPI File Adapter exactly once procedure fails explains your issue. If the file begins to be proccesed before the communication channel downtime the PI retains internally a GUID to know that file was taken. Until the retain period doesn't finish,  the PI will never takes that file, when this time ends up the PI will take that file.

Regards.

[Former Member]

Hi All,

This could the reason as explained in the SAP note given by Iñaki Vila but unfortunately, I could not confirm the same as our logs got overwritten.

thank you all for your help..

Thanks,

Venkat

[Former Member]

Hi,

as Jörg said, you should assume some process was editing/opening that file keeping it hostaged. You could try see the details at properties by right clicking in that file, so you could see the timestamps and editing time in order to compare them to the exact time the 5 min shutdown took.

Cheers,

Edu

[subhro_de]

Hi Venkat,

Which version of PI are you using - if it is PI 7.3 you may want to check the NWA-> Logs and Traces and look for errors during this period for thread errors or duplicate exceptions.

Regards

Subhro

[Former Member]

Hi Subhro,

We are using PI 7.31 ..I had identified the reason for not picking up the file in Log viewer Of NWA only (on Friday 11 Oct 2013). But now when I try to search for errors, there is no error at the time when the files are being picked up. . the channel was in time out for few mins only ..Later it was up and processing other files which are available in the folder except the one which has not been picked up at the time out error point.

Please share your views.

Thanks,

Venkat

[Former Member]

Hello Venkat,

could it be that some process was still reading (or trying to read) on that file? PI will not process a file which is currently used by another process. This way it is impossible that PI picks up a file which is just half-written or in process of deletion, for example.

In your case I would assume that this process keeps that file as a "hostage" for two days before releasing it for PI to process. Maybe you can check PI threads if some of them is running for a long time. Or you check on the file itself whether some process is using it.

Regards,

Jörg

[Former Member]

Hi Jorg,

User has informed us that file was placed at a particular time and it was not picked up by the interface (due to time out) .

Also if the issue due to the point that you are referring (editing mode/ incomplete mode ) ,  It could be one of the reason. But the point is the file was picked up by the channel after two days.

Could it be possible that the file is being used by someone through out this time window??

And Also there was some maintenance activity during 2 days . Could it be the reason?? But in that case also, there was no other failures for the same ..

Please share your views.

Thanks,

Venkat

[Former Member]

Hello Venkat,

I don't know what exactly happened, but this seems to me the only logical explanation. It could be that PI itself was still busy somehow on the file, maybe the timeout didn't cancel the process working on the file properly. This is surely odd behaviour that generally shouldn't occur.

Can you reproduce the error? On a test system, maybe? Then you can make further tests and observations. Otherwise, I'd recommend you to drop it until something similar occurs again. It might have been a singular incident and it is very hard to reproduce or trace all system settings for that short period of time.

Regards,

Jörg