Messages Stuck in Java Queues

[former_member186851]

Hello Team,

In production system,Messages are stuck in Java queue-DispatchDip with "to be delivered status"

The number of threads for this queue is 1.

After restart the messages are going.

What could be the reason and how to avoid restarting the system everytime And this is not happening for a particular interface its all random.

Please suggest."

[former_member184720]

What is your PI version? Have a look at the below note and see if it is applicable to your release

1986690 - PI messages stuck in status To Be Delivered in the dispatchDisp queue

[former_member186851]

Hello Hareesh,

Thanks for the assistance

version is PI 7.1

[former_member186851]

Hareesh,

I guess the note is for SAP PI > 7.3

Any notes for versions less than that?

[nitindeshpande]

Hello Raghu,

Messages get stuck in To Be Delivered status, if there are any messages using QOS as EOIO are in system Error. Try to find that Error message and cancel it.

Once you cancel the system error messages, all the other messages will be automatically processed.

If you do not find any messages in System error, then the issue might be due to overloading of the system and PI is unable to processes the huge number of messages hitting the Adapter engine at once. Permanent resolution for this is to have 2 server nodes for each server of PI system.

Considering you have one Primary Application Server (PAS), also termed as Central Instance (CI) and one secondary application server Secondary Application Server (SAS), then SAP best practices suggests to have 2 server nodes for each server. Hence you will have in total 4 server nodes. These server nodes will help you process the messages in an effective way.

If still this message does not serve your purpose and still you are facing issues, then SAP suggests to go for SAP web dispatcher or any other 3rd party load balancer which helps you to route the messages through each server nodes resulting in effective communication.

Please note, i have suggested the methods for permanent fix.

If your client is not spending for more efforts to be spent on this, then you can always try to find out the System Error message of EOIO based queue processing and cancel it. If you dont find any such error message, then the reason is surely about the performance and you must think of above methods of resolving it.

Regards,

Nitin Deshpande

[former_member186851]

Thanks Nitin.