Skip to Content

SMQ1 - Entry stuck - How to cancel that message(not Delete LUW option)

Experts,

1)

I just want to cancel message which stuck at smq1- qRFC queue in PI system.

Error: Error when opening an RFC connection (spefically we removed RFC to stop this message).

I would like to cancel this message. How can i do that?

I can change RFC connection pointing to dummy ECC server, so that message will be cleared automatically. But i am just curious is there any way to cancel this message.

I do not want to use Delete LUW option to clear this entry (I feel that Delete LUW is not good option).

2) same way for smq2 - if any entry stuck, is there any way to cancel those entry?

Error: BPE permanent error. after moving this error entry to SMQ3 and restore back in smq2, getting same error.

I just want to how to cancel these messages.

I already read and followed this procedure ie Peter Plumbohm reply from this thread.

old-messages-stucked-in-tbdl-status-to-be-delivere

u2026u2026u2026..

first and foremost the suggestion in this thread to delete entries from SMQ2 is absolutely wrong. This should never be done under any circumstances.

If you need to remove a queue entry because it is blocking the following messages, then you should use the function 'save LUW' in SMQ2 and not delete. This will temporarily remove the entry from SMQ2 and it will now be visible in SMQ3. After the problem with this LUW has been resolved you can 'restore' the entry from SMQ3 back into SMQ2 for further processing.

There is a direct link between the ABAP persistence layer for the XML messages and the qRFC entries. If you delete the qRFC entry (which you do by deleting the entry in SMQ2) then you create an inconsistency that can not be resolved. That is why the report RSXMB_CHECK_MSG_QUEUE was created (see Note 688147), in order to be able to cancel messages with missing RFC entries.

So, once again DON'T DO IT !

From the original description of your problem, you had run the report RSXMB_CHECK_MSG_QUEUE already, but was that before or after you deleted an entry from SMQ2 ?

As a next step, I would recommend to use the mdt (mesage display tool) in the Java stack to find and cancel the offending message. The mdt can be accessed through the URL http://<PI host>:<port>/mdt

If you find the message here, use the cancel button to set the message to 'failed'.

I would then re-run the report SXMS_REFRESH_ADAPTER_STATUS and check whether the message has then the appropriate status in SXI_MONITOR.

Thanks

Praba

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Dec 03, 2010 at 11:11 AM

    Hello Friend,

    Select the messages and click on the Pencil button on the tool bar in the pi screen .

    Regards,

    Ravi.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Ravi,

      In SXI_MONITOR, this message processed successfully. We can not cancel the messages using Pencil Button in sxi_monitor.

      This is already processed successfully by adapter engine.

      Pencil Button: Cancel Processing of messages with errors

      Thanks

      Praba

      Edited by: Prabaharan Rangasamy on Dec 8, 2010 6:09 PM

  • avatar image
    Former Member
    Dec 03, 2010 at 11:19 AM

    Hi,

    First save the LUW from SMQ2. Then it will be removed from the queue and go to SMQ3.

    Once you save the entry from SMQ2 then you can easily cancel the same message from SXMB_MONI as you do normally for error messages.

    Means once you save the entry from SMQ2 then it will allow to cancel that particular message.

    regards,

    francis

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 07, 2011 at 05:38 PM

    Thanks

    Add comment
    10|10000 characters needed characters exceeded