Skip to Content
avatar image
Former Member

messages stuck in the queue... how do I make them to be processed again?

Hi,

I'm new to SAP PI and kinda confused with queues.

I have file -> bpm -> file scenario and there was an error in mapping within bpm process.

When I went to qRFC Monitor (smq2), I see that in XBQO$PE_WS90000002 queue,

there's an error, 'Permanent error in BPE inbound processing'... which is expected.

Now, I run the interface scenario again several times but they don't get processed

but stuck in the same queue. At this stage, I didn't know what to do...

I thought by deleting the error message, other messages will be processed...

I deleted the error message but the other messages are still in the queue...

I have two questoins.

1. What is the best way to handle an error in the queue... can I just delete it? or is there a better way to handle an error in the queue?

2. After deleting the queue, what should I do to make the other messages to be processed again...

Thank you.

-Won

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Oct 05, 2010 at 11:22 PM

    This is BPM exception, you should have exception handler in BPM to catch the exception.

    Now you need to execute T-Code SWWL to delete the process manually, since there is BPM instance running and not terminated properly.

    For SMQ2, if this is not production, you can delete the LUW, otherwise, you have to handle the error.

    Regards

    Liang

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Won,

      Best practice would dictate that instead of deleting the LUW, you select the 'Save LUW' first. Then unlock the queue with activation (F5). This would then ensure that any other messages in the queue are not held up by a single erroneous message.

      You can then go back to the erroneous message (that you saved) using TCode SMQ3 to identify what raised the exception. From the queue you can actually drill down & trace each step in the BPM process up until the point that the exception was raised (which usually is a mapping error). You can then take the payload from that point & run it through your interface mapping to re-create the exception & fix the mapping that way. Once the mapping is fixed & activated you can re-submit the message from SMQ3 so that the message is processed successfully.

      Regards, Trevor

  • avatar image
    Former Member
    Oct 06, 2010 at 05:50 AM

    Hi,

    Go through below blog my Michael, it will give you clear picture

    XI : How to Re-Process failed XI Messages Automatically

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

    Regards

    pradeep P N

    Add comment
    10|10000 characters needed characters exceeded