Cannot change the status (amend/cancel/resend) of a PI 'Holding' message

[Former Member]

Hello,

We have a message within PI with status 'Holding' that cannot be edited, resent on cancelled in our PI (PLV(290)) LIVE system. This message has been set up with "Exactly Once In Order" delivery semantics and all its predecessors have been delivered and have status 'successful". This message dated on the 07/07/2009 is causing all subsequent jobs to remain in the 'holding' status. This is affecting our on-line payments and applications for students.

There are no errors (all chequered flags) when viewing the messages through the Integration Engine - Monitoring (SXMB_MONI). If we try 'cancelling the message with errors' through the this we get 'cannot cancel this message with this status'.

Through the Runtime Workbench if I try and 'resend' the message I get 'All messages retried successfully; update the status', however the status remains 'holding' even after a refresh. If I try and edit the message through the message editor I get 'Message editor can only be used for asynchronous XI messages that can be restarted'. If I try and cancel the message I get 'Unable to cancel 1 of 1 messages; update the status'.

Holding 07.07.2009 02:00:34 SITS_LIVE http://nspace.le.ac.uk/sap/xi/I_TRIBAL_SITS_MD/v1_0/sce StudentCurrentEnrolmentData UNICORN_Live http://nspace.le.ac.uk/sap/xi/I_SDU_MD/v1_0/student StudentCurrentEnrolmentLibrary_DL_TCPG

Holding 07.07.2009 02:00:34 SITS_LIVE http://nspace.le.ac.uk/sap/xi/I_TRIBAL_SITS_MD/v1_0/sce StudentCurrentEnrolmentData URDB_Live http://nspace.le.ac.uk/sap/xi/I_UOL_URDB_MASTERDATA/student StudentCurrentEnrolmentURDB

We are looking to cancel/amend or resend the u2018holdingu2019 message on the 07.07.2009 but cannot seem to do so with the Runtime Workbench or the Monitor for processed XML messages.

Any help would be appreciated

Jit Jauhal

University of Leicester

[former_member181962 · Accepted solution]

Hi,

See the answer to question 2 in this link:

http://sapxipi.blogspot.com/2009/06/qa-for-pi-one-stop-for-all.html

Regards,

Ravi

[Former Member]

Many thanks for the links. We assumed that if a message has the status u2018Successfulu2019 in the runtime workbench that it is complete and is in its final state (DLVD or FAIL) but this is not always the case. Viewing the sequential numbers allowed us to identify and fix the message that was causing the problem and the rest of the 'holding' jobs then ran to completion.

Thanks once again

Jit

[former_member185881]

Hi

See this blog and solve your problem

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

I hope this is helpfull to you.

Regards

Dheeraj Kumar