File Sender Communication channel with error

[Former Member]

Hi,

One of the File sender CC is in red but shows "Functioning". But in the Process Detail section it just showing

5/10/11 2:24:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds

5/10/11 2:24:00 AM Processing started

5/10/11 2:23:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds

5/10/11 2:23:00 AM Processing started

5/10/11 2:22:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds

5/10/11 2:22:00 AM Processing started

Please let me know is there any error with my channel ot wny is it red then?

There is no Polling step in the Process Details.. Please reply ASAP

Thanks,

Shweta.

[Former Member · Accepted solution]

Ur channel is lock. Try to remove the lock from NWA.. but first try to stop/start ur CC and chk if it works or not??

[Former Member · Accepted solution]

I did...stop..start but still it shows the same. I have checked there are no Java locks .

But the channel is in red and showing only two steps as i explained in my first msg.

Shweta

[Former Member · Accepted solution]

Hi Shwetha,

Please go through the below link:

The similar issue has been resolved in the above link.

Hope it helps.

Regards,

Subbu

[Former Member · Accepted solution]

I checked the link you sent ..it again talks abut the lock ..But I have already checked there are no locks.

Shweta.

[Former Member · Accepted solution]

Channel is working fine? Because probably red status refer to an old error...

[Former Member · Accepted solution]

The Status of the channel is "Processing Erros in last 20 seconds". And in the processing deatils it just show the below two steps.

5/10/11 2:24:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds

5/10/11 2:24:00 AM Processing started

5/10/11 2:23:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds

5/10/11 2:23:00 AM Processing started

5/10/11 2:22:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds

5/10/11 2:22:00 AM Processing started

It is continuasly showing the same message ID "d28c6542-0d7e-453b-1d96-9e0a18159315 " but this ID does not exist in SXMB_moni not in RTW message monitoring.

If I double click the message ID shown in the CC process details it shoes me below content.

Time Stamp Type Description

2011-05-09 22:03:00 Information Channel FileSenderGeneric: Converted complete file content to XML format.

2011-05-09 22:04:00 Information Channel FileSenderGeneric: Converted complete file content to XML format.

2011-05-09 22:05:00 Information Channel FileSenderGeneric: Converted complete file content to XML format.

2011-05-09 22:06:00 Information Channel FileSenderGeneric: Converted complete file content to XML format.

Please tell me what is the problem. there are No java Locks ...I have checked that.

Shweta.

[Former Member · Accepted solution]

Have you tried to perform a complete cache refresh?

[Former Member · Accepted solution]

HI Shweta ,

I faced the similar issue when the CC was working but it shows the old error . U have to make some dummy change in the communication channel in ID and then activate it . ensure in cache notification every thing is green then I hope the old error should be get removed .

Regards,

Saurabh

[naveen_chichili · Accepted solution]

Hi Swetha,

Make some dummy changes in your channel configuration as suggested by saurabh and activate your channel.Als refresh your cache and then try to check your channel monitoring you would be able to see the log if your message id.

Thanks,

Naveen.

[Former Member]

Hi

Thanks for your replies. Though the channel was showing only these two steps but when the file was placed in the source directory the interface was working and the channel turned to green. SO I am closing this.

Shweta.

[former_member186158]

It looks like a dead lock. The process start, but not complete or end,

Is there a big file which leads to time out?

[Eoin_Kierans]

Can you check if the SAP note #1483974 'File and JDBC sender adapter's retry not working after error' is applicable in this case.