IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting administration tasks and tools > Troubleshooting BPEL processes and human tasks > Troubleshooting the execution of BPEL processes
A long-running BPEL process appears to have stopped
A long-running process is in the state running, but it appears that it is doing nothing.
Reason
There are various possible reasons for such behavior:
- A navigation message has been retried too many times and has been moved to the retention or hold queue.
- A reply message from the Service Component Architecture infrastructure failed repeatedly.
- The process is waiting for an event, timeout, or for a long-running invocation or task to return.
- An activity in the process is in the stopped state.
Resolution
Each of the possible reasons requires different corrective actions:
- Use the failed event manager console to display details about a failed message and to replay it.
- Check if there are any failed message in the failed event management view of the administrative console.
- If there are any failed events from Service Component Architecture (SCA) reply messages, reactivate the messages.
- Otherwise, either force complete or force retry the long-running activity.
- Check if there are activities in the stopped state, and repair these activities. If your system log contains a CWWBE0057I message you might also need to correct your model as described in Message: CWWBE0057I.
Troubleshooting the execution of BPEL processes
Related concepts:
Finding failed events
Manage events
Related tasks:
Forcing the completion of activities