Adapter message monitoring: message in HOLD

[Former Member]

Hi,

since we changed a scenario:

a) old scenario: R/3 --> XI --> BPM --> XI --> FTP

b) new scenario R/3 --> XI --> FTP

the messages stuck in adapter message monitoring.

Message-Interface is the same, CC is the same; just the way through BPM was canceled.

any suggestions?

Thanks

Regards Mario

[aashish_sinha · Accepted solution]

HI ,

Please refer these two threads,

/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

hope this will help you.

Regards

Aashish Sinha

PS : reward points if helpful

[Former Member]

Hi,

we changed our modifications to an older version of the receiver determination, actitiveted, the made the modification again with a new communication channel.

Now it works.

Thanks a lot

Regards Mario

[Former Member]

Hi Mario,

messages are in status HOLD, when they need to be sent in exact order (EOIO), and an error occured in one (or more) queues. When you solve this error, restart the first message from the queue after this error and the items will be processed.

How to do that:

Go to messaging system servlet, find your message (in hold status) and click the Eye icon - Details. Now read the Conversation ID value - which is your queue ID.

Go to RWB, message monitoring, choose adapter engine( from combobox)-> display.Now click additional criteria, put the value of Conversation ID to conversation ID textbox. Start search. You'll see a lot of messages there in hold status I think, But find the one in System Error status. Try to resend this message, if it will not change its status (will still be in in System error), cancel it. Now restart first message from the queue, which was after this wrong one.

This should release the queue and process items.

If any questions, let me know.

Peter