Restarting Queue not allowed in PI

[Former Member]

Hi all,

I have a queue with status "sysfail", so a lot of messages are stuck. In [url]http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2728[ [original link is broken] [original link is broken] [original link is broken];url] i am told, that I should restart the queue. To be able to do so, i need to set the parameter QRFC_RESTART_ALLOWED to 1. The system help says the following:

Parameter QRFC_RESTART_ALLOWED

Meaning

The parameter defines whether it is permitted to restart processing of a failed message in the qRFC monitor (transaction SMQR). If it is not permitted, an error occurs in the runtime.

This must only be permitted in exceptional cases since it does not follow the usual restart procedure in the monitor of the Integration Engine.

Now my question is: What would be the usual restart procedure? And should I do It in the described way anyway?

KR

Felix

[Former Member · Accepted solution]

Hi Felix,

Normal restart of a message is to restart from the Integration Engine i.e SXMB_MONI.

Yes, you need to follow the proceedure provided in the link to reprocess the messages.

Please ref: http://www.saptechnical .com/Tutorials/XI/Configuration/IEValues.htm

Thanks,

[former_member854360]

Hi Felix,

You can use

RSQOWKEX --> QOUT Scheduler: Execution of Registered Outbound Queues

OR

RSQIWKEX - -> Standard QIN Scheduler: Execution of Registered Inbound Queue

These are available in PI 7.1.

Please see this Blog

/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i

http://help.sap.com/saphelp_nw04/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm

[Former Member]

Hi Debashish,

thanks for the very quick and helpful reply. The PI I use is a 7.1 - but the system cannot find the tcodes you mentioned. Or did you not refer to tcodes? What do I miss?

[former_member854360]

Hi Felix,

Those are the standard report Name.

Go to SE38 transaction and search for those reports.

You need to schedue those reports for automatic restart of failed messages.

Or

You can manually execute.

[Former Member]

Hi,

RSQOWKEX and RSQIWKEX are standard SAP programs and not tcodes. Goto tcode se38 and execute the same.

Regards

[naveen_chichili]

Hi Felix,

Please go through the blog:/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

---> Try to Unlock the queue and try to reprocess the message it will get processed

if you are unable to process then

By using the transaction SMQ2 you can reset the queue's status.

Set IS configuration parameter MONITOR QRFC_RESTART_ALLOWED to value 1.This will initiate processing of messages stuck in the queue

You can run RSQIWKEX to run periodically. It resets the queues automatically.

You have to go to SXMB_ADM. Then click manage Queues and you have to dergister all the queues. After doing this you need to go to SMQ2 and you have to actiavte the queues.

After all this try to re-register the queues in SXMB_ADM

[Former Member]

Hey,

after the procedure described in the link - the queue was in status "retry" and is now in status "sysfail" again. I cannot find the status "retry" in the documentation (but i can imagine...): http://help.sap.com/saphelp_nw04/helpdata/en/d9/b9f2407b937e7fe10000000a1550b0/content.htm

Is it possible to just delete the first luw in the queue that is causing the problem? The documentation says so. But it does not reveal how. Do you know? If I click on delete in smq2 do I delete the queue or the luw?

Edited by: Felix F. on Jul 19, 2011 6:23 PM

Edited by: Felix F. on Jul 19, 2011 6:26 PM

[Former Member]

double click on the queue name and then try to delete or save the first message having sysfail status(click on edit ->save or delete)...

[former_member854360]

HI Felix,

If you double click on any Queue entry then you can see all the message entry inside that queue.

now click on the sysfail entry then it will take you to SXMB_MONI particular corresponding faile message.

then cancel the message.

Automatic Cancel:

Here you GO:

If in case of bulk error messages, all these error messages can either be cancel them manually by selecting these set of messages in SXMB_MONI and then cancel them by pressing button "Cancel Processing of Messages With Error" (CTRL+F8). or report RSXMB_CANCEL_MESSAGES is the tool of choice for mass data handling, i.e. for canceling a large set of messages. This report handles message that already are in error state.

SE38 -

---

>RSXMB_CANCEL_MESSAGES

If you cancel the message using RSXMB_CANCEL_MESSAGES then it will be removed from the QUeUE.

RSXMB_CANCEL_NOT_REST_MESSAGES Cancel XI Messages With Errors That Cannot Be Restarted

we cannot cancel the messages which are in pending status. But there is a way by which we can bypass holding messages. For this, we need to go to SMQ2, select the queue, select holding message LUW and select the option to save LUW. We can restore these LUWs back from tcode SMQ3.

Also You may be find interesest in this Blog

/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework

URLs of help.sap.com

1) http://help.sap.com/saphelp_nw04s/helpdata/en/f5/d347ddec72274ca2abb0d7682c800b/frameset.htm

2) http://help.sap.com/saphelp_nw04s/helpdata/en/41/b715015ffc11d5b3ea0050da403d6a/frameset.htm

3) http://help.sap.com/saphelp_nw04s/helpdata/en/0e/80553b4d53273de10000000a114084/frameset.htm 

Edited by: Debashish Roy on Jul 19, 2011 6:44 PM

Edited by: Debashish Roy on Jul 19, 2011 6:47 PM

[naveen_chichili]

Hi Felix,

You double click on the queue and just rightclick on the first message having SYSFAIL and save LUV so that the message will be saved in SMQ3.

you would be able to see the saved message in smq3 and view and trouble shoot later and reprocess that message instead of holding all the messages in SMQ2.

after saving the first message the remaining messages will process automatically.

Regards,

Naveen

[former_member611181]

Felix,

Before deleting queue first check whether you are getting dumps in ST22, which will give more details.

Or Once you identify root cause and then if you determine you dont have any depend messages you can delete the queue which is stuck.

[Former Member]

Hey,

thanks for all the replies. Since the error seems to be of a more general nature, I posted a new thread. Thanks again.

Felix