Message Stuck in Queues SMQ2

[VCUNTHEE]

Hi All.

We are having a production issue where now and then, we have message accumulation which is visible in SMQ2. Messages accumulates upto 10000 in the queues. Most of the times the queues are outbound queues XBTO* and the status of the message is in "Scheduled for outbound processing".

There are no regular patterns in them, in terms of, when it occurs.

Any clue could be of great help.

Thanks

Vedavyas

[former_member193372]

Hi,

Regarding your error you just follw the below points:

if you face Blocked Queues (SYSFAIL), Incoming Messages are blocked then follow the steps

1.) Go to SMQ2 (qRFC monitor) and execute

2.) If there is a queue not moving, double click on queues ‘til you see the status. SYSFAIL due to error – move to the right to see the error text

If error is due to cache not refreshed:

1.) Go to transaction SXI_CACHE and check if CACHE is not up to date In this case, CACHE contents are up-to-date.

2.) If CACHE is not up to date, click Refresh before refreshing the cache just in case someone else already did it. If still not up to date, click “Start Delta Cache Refresh” in “XI Runtime Cache”.

If CACHE is already up to date as seen above, proceed to next steps.

3.) Then, go back to SMQ2. Unlock the queue that is in SYSFAIL. To do this:

a.) Choose the queue that is in SYSFAIL.

b.) Click unlock icon

4.) Then, double click in the queue name ‘til you go to the user.

5.) Double click on the user to go to the message in error

6.) Select the one in error

7.) Click restart and refresh to see if the message will be processed successful.

If error text is due to JCo failure (Java connector)

- When J2EE is already up, do the following:

1.) Just go inside the queue in error ‘til you go to the user.

2.) Double click on the user to go to the message in error.

3.) Click/Choose the message in error (just going to the right for the error message, it is JCo failure related)

4.) Restart the message (retaining the trace level)

6.) Check for the status of the XML if it is now processed.

7.) Then, click F3 or back ‘til you go back to the queue in SYSFAIL.

8.) Then, reset status of the LUW of the queue in SYSFAIL.

After that, it could be seen that queues are now in RUNNING status.

-

---

If helpful reward points pls

Thanks & Regards,

Venkata Nagesh B

[VCUNTHEE]

Hi Guys,

Thanks a lot for those responses. We have tried all the options that were suggested. Will update if we find any solution.

Thanks again,

Vedavyas

[Former Member]

Are you using BPM?If any mistake in the integration process step will lead this error

Because of this the remaining messages will also get stuck up into this Queue.

So try to delete the message that caused the error.

You Can see the error message in SMQ2

regards

Sreedivia

[sunil_singh13]

Restart your Communication Channel (Adapter Whichever u r using)

Yor problem will definetly get resolved

Thanks

Sunil Singh

[Former Member]

Hi,

Usually, you find the first LUW in the queue that led to an error during processing.

More details of the error are documented in the XML message corresponding to the

LUW. To find this message, double-click the TID of the LUW. Then you will either

see a screen from where you can get the message ID or forwards to the XML message directly.

The qRFC is sequential. So a message that could not be delivered will back log the rest of the queue.

You have to "drill down" into the queue to locate the first/oldest message in that queue and clear it's error. Then the rest of the queue will flow.

Scheduled status may come for different reasons,

1) Receivers are not ready

2) Queues are stuck up

3) Connection Problem

4) Waiting for the confirmation etc..

But it is prefer to check the status in the transaction SMQ2 in the XI box.

Also this blog may help u-

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

Thanks

Swarup

[ravi_raman2]

Hi,

Swarup is right..find the first one that hogs the queue`s then the rest will fall through..also check queue administration...

Regards

Ravi Raman

[VCUNTHEE]

Hi Swarup,

Thanks for the response the same steps we do, it was a helpful answer and i have awarded the points.We have been having this issue now and then, there are no specific message because of which it is failing, we did look in to the blog you refered ealie, but we are not sure if we can automate the RSQIWKEX which will clear the queue block when ever we have this situation. As in one of the SAP note it is clearly mentioned that we shouldnt automate this unless we have an issue with inbound queues activation. As it is running fine most of the time.

We are in PI7.0. SP12

Thanks,

Vedavyas

[Former Member]

Hi Vedavyas,

This kind of blockage happen based on the burden on Integration Server.

If the Integration Server is not overloded then this will not stuck up in Queue.

Probably You need to regularly refresh the cahce and have to do the maintenance activities to up-to date the performance of integration server.

Increase the Heap size, and Memory Utilization.

Thanks

Swarup

[VCUNTHEE]

Hi Swarup,

Thanks again. Do you mean FULL CACHE update or Delta cache update or something else.

Thanks,

Vedavyas

[nisarkhan_n]

Check the Delta refresh...u can set the CCMS alerts for the queues for aleting in any case of blockage....

in genereal several factors lead to the queue blockage most common is the IS taking time to process...or huge data or bad queue helding up other data,..

[Former Member]

Hi,

Goto RWB and search for messages in System error status. Try resending this message (By fixing the error). If the error for this message cannot be corrected at this stage then delete the message from queue, the remaining messages which will be Waiting state will start running if the issue is resolved. Be carefull there will some messages in Holding state. If you resend the first message of this reaming will folllow.

Nagesh!!!