Stucked messages in SXI_MONITOR after system restart

[Former Member]

We are facing an issue we can't solve on our own and didn't found related information in OSS.

In the system SAP PI ( Java and or ABAP part) we can see stucked messages in SXI_MONITOR after a system restart ( doesn't matter the reason - unexpected restart mostly due to hanging java node. etc )

Once we want to restart the messages from SXI_MONITOR it appears messages are already scheduled in Queue and can't be

restart over SXI_MONITOR. But due to the restart the queues are empty in SMQ2 /SMQ1. So restart over the queues can't be done.

Is there a way to restart the messages in the PI system once this situation happens.

Any help appreciated.

[Former Member · Accepted solution]

Sap came back with the following OSS Notes which solved the problem.

0001547908 XI Runtime: Message restart impossible after dump

0001552345 XI Runtime: Restart impossible after dump II

0001562456 XI Runtime: Message restart impossible after dump III

0001592475 XI runtime: No message restart after dump IV

[Former Member]

Hi,

Have you checked the queues are registered (R) state afte restart of the system..?

Also check the Queue which is used by the message you trying to restart ..

Note : if the messages are synchronous ones and you are trying to restart them then the behaviour is as expected..

HTH

Rajesh

[Former Member]

Queue are in state registered but empty.

There a partially synchron  messages. But there are also asynchron message with the same error.

No restart nor cancellation of the message possible with standard monitoring tools.

Is  there a way how this can be avoided or these message can be treated in a special way  ?

[Former Member]

this is somewhat of inconsistency situation, you need to cancle it  , then resend it...

if can't be resend from app system, take the payload and send using RWB test msg.... not recommended but can be used if no other way out..

[Former Member]

Cancelation of these message seem as well impossible in the SXI_MONITOR.

Same message apear "Message is already scheduled. "

Which is odd because that means  we need to cancel it over special report which has no good selection criteria to only resent these.