How to Analyze Stopped Queues in Status “SYSFAIL” in PI ccBPM

Introduction

One of the common problems when using ccBPM (cross-component Business Process Management) in SAP Exchange Infrastructure or SAP Process Integration is that in some error situations the inbound queues in transaction SMQ2 are stopped and set to status ‘SYSFAIL’ with the error message ‘Permanent error in BPE Inbound Processing’.

– Please do not mix up with queues that temporarily have status “STOP”, this is caused by concurrent running deadline job SWWDHEX and is not an error (see also SAP note 1050827 about it).-

When this happens all following inbound messages for this Integration Process are stopped as well waiting in the blocked queue. So this is a huge problem for customers and this article describes how to find the reason for this problem by using the Support Tool functionality and gives also advice on how to change the configuration or process definition so that the problem does not happen again.

Symptoms

In transaction SMQ2 there are queues that are named XBQO$PE_WS* or XBPE_WS* on status ‘SYSFAIL’.

‘WS*’ stands here for the task name of the process where the message should be delivered to. In transaction SXMB_MONI there are messages with Outbound Status ‘Message scheduled on outbound side’ (green flag) or ‘Message has error status on outbound side’ (red flag). By clicking on ‘PE’ in column ‘Outbound’ the qRFC Monitor with the blocked queue is shown. When this error happens all following inbound messages for this process type are stopped as well waiting in the blocked queue.

System Analysis using the Support Tool

To display the stopped queue use transaction SMQ2 or navigate to the stopped queue from transaction SXMB_MONI by clicking on ‘PE’ or ‘SA_COMM’ hotspot in ‘Outbound’ column. Double click the queue name to display the relevant queue where you see the status text ‘Permanent Error in BPE Inbound Processing’as first entry:

By double clicking on this status text, you reach the support tool, which provides all important information about the process and also important functionality for support purposes such as display of trace or the possibility to simulate the message delivery:

First you can execute the function ‘Display Trace’ to check if the trace provides a detailed error description:

When the trace alone does not provide enough information, please return to the Support Tool and execute ‘Simulate Message Delivery’. The Result of Message Delivery Simulation shows then the error during delivery and also the process instance(s) the message would be delivered to if there are any.

It is also possible to display the workflow protocol of the process instance(s).

did you try the ‘Simulate Message Delivery’ function? Then the process instance ID should be displayed as well. I guess the respective process instance is in status ‘ERROR’. You should check why the error happened in the workflow log (transaction SWI1) and – depending on if the error is resolvable or not – restart the process instance via transaction SWF_XI_SWPR or logically delete it (e.g. via note 1286336).

I notice Workflow error in SWF_XI_SWPR. I found that i maintain wrong correlation. Now i have resolved the issue and correlation is same. But i cant able to restart the workflow. Getting same workflow ‘error’ status in SWF_XI_SWPR. But in SWWL no workflow is found for deleting the workflow. How to resolve this issue. Please help me.

you should logically delete the workflow. If note 1286336 is implemented in your system you can use transaction SWIA, specify the workflow ID to select it, then mark it and choose ‘Edit->Workitem->Logically Delete’. If the note is not implemented then please follow the instructions of note 807906.