Scheduled for Outbound processing - SMQ2 has 0 entries!

[Former Member]

Hi !

After a XI server reboot because of a JCO communication failure, there were a lot of messages stuck in queues. We executed manually the LUWs and everything went ok, but we still have some messages with "Scheduled for Outbound processing" status in SXMB_MONI (right black arrow icon) and its queues are all empty via SMQ2.

Those messages were sent EOIO.

What should we do? restart manually each message in order?

Thanks!

Regards,

Matias.

[prateek · Accepted solution]

First check the status of the messages in RWB

For EOIO, see this

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

See this

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

Regards,

Prateek

[Former Member]

Prateek/Sreenivas

Thanks!

In RWB, the messages have the status WAITING. This messages are all in the component Integration Engine.

Regards,

Matias.

[Former Member]

Hi Matias,

What did the audit log say ?? under description do you see these:

The message status set to DLNG

The message was successfully transmitted to endpoint

Regards,

Sreenivas

[Former Member]

Hi Sreenivas!

There is no audit log, because the message with Waiting status is in Integration Engine, not in Adapter Engine. The audit log for the process of getting the message to enter XI went OK, all steps are in Success in audit log...but there is no audit log for "leaving" XI.

If I restart each message manually, they go ok...is there any way to ensure the EOIO order and make XI to resend them in order?

Regards,

Matias.

[Former Member]

Hi Matias,

>>any way to ensure the EOIO order and make XI to resend them in order?

You can schedule this RSXMB_RESTART_MESSAGES.

Regards,

Sreenivas

[Former Member]

Matias,

Also have a look at this blog

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

Regards,

Sreenivas

[Former Member]

Thanks !

I've restarted manually the messages. But still don't understand why being them async and persisted, they were not stuck in any queues!! and still scheduled for outbound processing.

Regards,

Matias.

[Former Member]

Hi Matias,

"Scheduled for Outbound processing" means the message is delivered to the receiver system and XI is waiting for the acknowledgement or response from the receiver. In this case your SMQ2 will be empty.

Check in RWB for the status of these messages in message monitoring what does it say ?? time out ??

Can you tell me what are the scenarios that have the status "Scheduled for Outbound processing"

Regards,

Sreenivas