Undelivered messages (holding status)

[Former Member]

All,

In our scenario we have a one incoming message being sent to 3 different receivers/interfaces. (2 files and 1 mail - using 3 different mappings).

the scenario is working right... but in a test today morning. we found that the output files or mails were not sent. All the messages are successfully processed in SXMB_MONI (no errors). All the communication channels are green.

When we checked the message monitor - we found that the status for all the 3 messages was "Holding". Even when i try to redeliver it - it comes back to the status of holding.

we tried running the scenario again and it is working... the question is how do we get the files/emails for the earlier run?

Thanks.

[justin_santhanam · Accepted solution]

Hi,

Did u checked what's the error in audit log?

-raj.

[Former Member · Accepted solution]

there is no error in the audit log - all it says is it picked up from the receive queue, and then it put back in the hold queue.

thanks,

[Former Member · Accepted solution]

Check this note - 885879. The predecessors might be in "Not Delivered" status. Once you delete them manually in MDT, try re-processing the messages with "Holding" status.

<krr>

[bhavesh_kantilal]

Hi,

In the interface determination , deselect option <b>Maintain Interface Order at Runtime</b>

and then test things. They'll now work fine.

Regards

Bhavesh

[Former Member]

Hey

well a lot of times what happens it that XI is unable to make proper connection for the first time u run the scenario coz the communication channels have been sleeping for past several hours and it takes a bit of time to establish the connection,but later on once the connection is established then we don't see any problem.

as suggested by Raj check the logs as well as did u get any HTTP_TIMEOUT errors?

just try to drill down the messages and sxmb_moni and see if XI retired to establish the connection

Thanx

Aamir

[Former Member]

Hi,

This happens in the case of EOIO scenarios, If the earlier message is not delivered, further messages wont be delivered as well.

http://help.sap.com/saphelp_nw04/helpdata/en/49/e3fb40ef74f823e10000000a155106/content.htm

Go TO RWB, and check all the messages sent out from XI for this interface.

Some message sent earlier may be in error status.

cancel that using the CANCEL button.

else, you cancel all the messages for this interface, since this is test environ.

You cant do the same in production

Lets give it a try..

Regards

Pushkar

Message was edited by:

Pushkar Anand

[Former Member]

I tried cancelling and this is the error im getting...

com.sap.aii.af.ra.ms.impl.app.AdminException: Failed to cancel the message locally. Reason: Could not fail message 46cd6558-c769-4e25-e100-0000a628ff7d(INBOUND), as triggered by admin action. Reason: Predecessor not in final state.

How do we find which is the predecessor for this message?

the other thing i noted is - in the sucessful ones, the sequence in the "Message Data" is 1,2,3. In the one instance, where it is in holding state - it is in 4,5,6.

Thanks.

[Former Member]

Hey

>>How do we find which is the predecessor for this message?

you can find that in sxmb_moni,coz the messages are processed sequentially so just look at the time and the MsdID

Thanx

Aamir