Queue blocked after BPM error!

[Former Member]

Hi,

Is there any configuration steps to do in order to avoid incoming message to be blocked (Scheduled on outbound side) in the queue when there is a bpm error.

Thanks in advance,

[Former Member]

Hi,

yes we can do through SXMB_ADMIN, SMQ1..

Outbound Scheduler (Transaction SMQS)

If the Outbound Scheduler is responsible for sending and executing these LUWs, and the logon data in transaction SM59 in the destination is incomplete, then any subsequent LUW calls might be executed under the logon data of a previous user. This occurs if the destination scheduler is already running under another user when the LUW is called and no logon data is maintained in transaction SM59. In this case, the destination scheduler runs under the user that started the scheduler (and this user's language). This means the destination scheduler runs under the wrong logon data, as does the processing of the subsequent LUWs.

Until now, destinations could only be registered in the Outbound Scheduler if the logon data (client, user, password, language) had been defined completely in transaction SM59 (if LUWs always needed to be processed under a specific user and language). Destinations with incomplete logon data could be registered only if the user and language was not important. In addition, some internal destinations (NONE/SPACE) do not allow you to enter a user or language in transaction SM59. For this reason, and for tRFC compatibility, you can only register these destinations in the Outbound Scheduler with the optional Without tRFC flag.

see below links

http://help.sap.com/saphelp_nw04/helpdata/en/1a/d2fc40b2c7f96fe10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/ba/665f3c482a7331e10000000a114084/frameset.htm

Regards

Chilla..

[Former Member]

Thanks for information,

I m not looking where the problem coming from but how to avoid to have a blocking queue regardless the problem source.

Regards,

FF

[Former Member]

One thing you can do is to schedule a report on XI - RSQIWKEX - this restarts the queues that are blocked...before that an integration engine parameter needs to be set...

all these are talked about in the following blog...

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

Moorthy had already posted this link in his reply..so if you looked at it already and your question is something else...please ignore...

[moorthy]

Hi,

This error may be because of many reasons.

1. Huge volume of data

2. Previous message queue has got stucked

3. Message is in Process Status- ie not completed

4. connection failure

ets.

1) first , hope u have registered the queue in SMQR

2) Check the staus of queue in the SMQ2

3) Try to schedule/restart the queue

This blog may help u-

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

Hope this helps,

Regards,

Moorthy

[Former Member]

Cube,

Follow this weblog which will resolve your issue:

/people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi

Also check this for some information:

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

/people/riccardo.miggiano2/blog/2006/12/01/dynamic-serialization-of-messages-with-qrfc

/people/riyaz.sayyad/blog/2006/12/08/dealing-with-errors-on-the-outbound-side

---Satish