I wanted to share with SCN members, the below Technical Problem that we overcame. so that it helps resolve the problem as quickly as possible. as we took more than a week to resolve it. but it was quality system.
We had a situation, where millions of messages/files stuck in PI as a result it bought down the server. the messages were stuck because the first messages failed and subsequent messages were in 'hold' status, as these messages were EOIO.
Tried to resolve the problem uisng front end tool RWB.
canceled errored messages and tried to do "repeat" but those millions of messages gets the system down again and again.
never could processe all those messages.
Got SAP's help as below:
The best option to resolve the problem would be to fix the root cause
for the failure of the first message in EOIO interface
serialization context. You can find this blocking message in
http://<host>:<port>/MessagingSystem/monitor/sequenceMonitor.jsp.
If you resend or fail this message (if error message then 'fail' it, next message "resend' it)
and the problem is resolved allconsequtive messages will be resent automatically.
You cannot cancel all these million messages at once from the Monitoring tools as they
trigger the cancelation of messages one by one. For EOIO messages
cancelation will be successful only if the order in which they are
cancelled is according to their serialization context and serial
number - for each message the predecessor should be in final state.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.