Queue blocked after BPM error!

Question

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,

Answer 1

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
The reason of blocking a queue
Queues getting blocked on error
Regards
Chilla..