Cutover Activities in Progress - Message Status To be Delivered - Stuck

[Former Member]

Hi

Cutover Activities in Progress - Test Message Status To be Delivered Stuck in Adapter Engine . Its a File to File with BPM Scenario . File is getting picked up BPM Works Absolutely fine and the SXMB_MONI with checkered Flags . Message Not received in Reveiver File Communication Channel .

When i dig into Message Monitoning i ifnd that message is with the Status "To be Delivered" . All queues are fine nothing stuck .

Checked for the permisions to write the file everything is fine and even changed it to write it to /usr/sap/tmp . In any case message goes to TO BE DELIVERED . Appreciate any Help . As time is running out .

Thanks

Sudhir

Edited by: Sudhir Medapati on Sep 24, 2009 12:15 AM

[Former Member · Accepted solution]

Hi Sudhir.

Go to RWB --> component monitoring --> adapter engine --> communication channel monitoring --> put your receiver file comm. channel and name and then click on use fileter --> there you should see for any errors. Something you should find there.

Regards,

---Satish

[Former Member · Accepted solution]

There is no Trace in the Communication Channel Logs . I could only find status in the message monitoring . Its not even delivred to Communication Channel . Its stuck in the adpter Engine . Thank for ur quick reply

[Former Member · Accepted solution]

Hi Sudhir,

There may be problem in BPM. See the workflow log in BPM.

Regards,

---Satish

[Former Member · Accepted solution]

BPM Looks absolutely fine . I have a Email Receiver also inside this BPM . It sends Email Perfectly .But only when its tring to use the File Adapter the Message is getting stuck . ... and the BPM Graphical Workflow log and Technical Details log looks absolute normal . All Green Light with Chckrd flag and Workflow Completed Status .

Message Monitoring Logs

where it tries to put a file .

2009-09-23 15:42:41.826 Success The message was successfully received by the messaging system. Protocol: XI URL: http://XXXX:XXXX/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2009-09-23 15:42:41.828 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2009-09-23 15:42:41.845 Success Message successfully put into the queue.

Where it tris to send an email

2009-09-23 15:19:43.873 Success The message was successfully received by the messaging system. Protocol: XI URL: http://sappip:54800/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2009-09-23 15:19:43.875 Success Using connection Mail_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2009-09-23 15:19:43.891 Success Message successfully put into the queue.

2009-09-23 15:19:43.892 Success The message was successfully retrieved from the receive queue.

2009-09-23 15:19:43.899 Success The message status was set to DLNG.

2009-09-23 15:19:43.899 Success Delivering to channel: CC_EMAIL_RECEIVER

2009-09-23 15:19:43.9 Success Mail: message entering the adapter

2009-09-23 15:19:43.9 Success Mail: Receiver adapter entered with qos ExactlyOnce

2009-09-23 15:19:43.9 Success Mail: calling the adpter for processing

2009-09-23 15:19:44.046 Success Mail: call completed

Edited by: Sudhir Medapati on Sep 24, 2009 12:43 AM

[Former Member · Accepted solution]

Hi Sudhir,

Since email is working and file is not working, try to put a file directory path which is currently working in the file receiver communication cahnnel and see. Also what did you put in directory path? You should see somehting in communication cahnnel monitoring. You said you are not having any logs which is wondering me. Do you have any file receiver communication channel working. If yes then put that path and see.

Regards,

---Satish

[Former Member · Accepted solution]

I tried changing the Fie Path /usr/sap/tmp that dint help. It dint make any difference .

I could find only below

Green Light Server 00 48_4896012 Functioning

There is no logs below this . Thanks Sathish for your continued support to help us .

[Former Member · Accepted solution]

Try giving //before usr. May be authorization issue so try creating a new folder and see

[Former Member · Accepted solution]

Looks like not an issue with Authorization . One weird thing i could see is in SXMB_MONI .

@DF\QProcessed successfully@ @5F@ 23.09.2009 17:22:21 17:22:21 IP_SPLIT_TRGREQ http://xxxxx.com/sap/xi/lms/trainingrequirements SI_TRGREQ_I_A_A BC_LMS

@DF\QProcessed successfully@ @5F@ 23.09.2009 17:22:21 17:22:21 CHANGECAST http://xxxxx.com/sap/xi/lms/trainingrequirements SI_TRGREQ_O_A IP_SPLIT_TRGREQ

Integration Process sending out to File Adapter is first entry and the Integration Process Receiving Message is shown as second in SXMB_MONI this is the only difference i could find between PIQ and PIP.

CHANGECAST ---> Integration Processs ---> BC_LMS SXMB_MONI Entry

suppose to be

@DF\QProcessed successfully@ @5F@ 23.09.2009 17:22:21 17:22:21 CHANGECAST http://xxxxx.com/sap/xi/lms/trainingrequirements SI_TRGREQ_O_A IP_SPLIT_TRGREQ

@DF\QProcessed successfully@ @5F@ 23.09.2009 17:22:21 17:22:21 IP_SPLIT_TRGREQ http://xxxxxx.com/sap/xi/lms/trainingrequirements SI_TRGREQ_I_A_A BC_LMS

Edited by: Sudhir Medapati on Sep 24, 2009 2:30 AM

Edited by: Sudhir Medapati on Sep 24, 2009 2:32 AM

[Former Member · Accepted solution]

give a try

Deactivate/Activate comm channel in ID

Start/stop channel from comm channel monitoring

[Former Member · Accepted solution]

Thanks Sathish & Arvind for your Enthusiasm to help on this issue.

The Message got stuck in the Adapter Engine and it set status as u201CTo be Deliveredu201D in the Message Monitoring. There was no log in the Communication Channel (Active and Error free). BPM was sending email for one of the case where it needs to send Email Notification.

We tried deleting Communication Channel and recreating it, changed the location where the file needs to write to check on Authorization issues nothing helped. Since it was a Production Server we had to go for a long approval process to justify for a system restart as we have quite a number of synchronous scenarios. Without any options left we did a System Restart and it worked. Hope this helps someone in future.

Thanks

Sudhir

Edited by: Sudhir Medapati on Sep 24, 2009 11:10 PM