cancel
Showing results for 
Search instead for 
Did you mean: 

[VERY URGENT]Messages going in Scheduled State

Former Member
0 Kudos

Hi Experts,

PROD ISSUE

All of sudden in PROD scenario all the messages start moving to Scheduled state in message monitoring and the channels have stopped polling . I have checked the dispatcher status in engine status (additional data tab) and find that the maximum thread count is 1.

Is that the issue? also any idea y this issue is happening and what can be checked and done in this case ?

URGENT HELP NEEDED !!!

Thanks in Advance

Accepted Solutions (1)

Accepted Solutions (1)

former_member192238
Participant
0 Kudos

Hi,

You should check your Inbound or Outbound queue in SMQ1 & SMQ2. The messages are stuck there.

Double click on message & read the error details & resolve the same.

Check SM58 also for problem.

Also Register & Activate (re-asctivate) your queues in SXMB_ADM --> Manage Queue --> Register Queue & Activate Queue.

If the messages are stuck in queue, First resolve the error in Queue & check the messages.

Go through this Link

http://www.saptechnical.com/Tutorials/XI/XMLMessageQueues/Monitor.htm

Hope this help

Regards

Praveen Reddy

Answers (3)

Answers (3)

prasanthi_chavala
Active Contributor
0 Kudos

Hi,

Check this blog to see if there are any stucked error messages.

Thanks,

Prasanthi.

anupam_ghosh2
Active Contributor
0 Kudos

Hi ,

This seems to be a problem of buffer size in PI. whenever there is lack of memory space the messages move to scheduled stage. Take help of your SAP BASIS team. Clear unnecessary files on server and check out buffer. BASIS team should be aware of all the transactions reqd for the purpose. Pi server running out of space might be causing this issue. You can have a look in this http://www.riyaz.net/blog/xipi-dealing-with-errors-on-the-outbound-side/sap/9/

regards

Anupam

naveen_chichili
Active Contributor
0 Kudos

Hi,

Check your Inbound and outbound Queues in TCODES: SMQ1 and SMQ2.

Also check if the re are any messages stucked in EOIO Queue in http://<hostname>:<port>/ MessagingSystem.

Regards,

Naveen