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
An activity has stopped because of an unhandled fault (Message: CWWBE0057I)
The system log contains a CWWBE0057I message, the process is in the state "running", but it does not proceed its navigation on the current path.
Reason
An activity is put in a stopped state, if all of the following happen:
- A fault is raised by either the activity's implementation or during the evaluation of a condition, timer, or counter value associated with the activity, for example, its join condition or any of the transition conditions of its outgoing links.
- The fault is not handled on the enclosing scope.
- For invoke activities, inline human tasks, and Java snippets, if either of the following happens:
- The continueOnError attribute of the process is set to no and the continueOnError attribute of the activity is set to inherit or no.
- The continueOnError attribute of the process is set to yes and the continueOnError attribute of the activity is set to no.
- For all other activities, the continueOnError attribute of the process is set to no.
Resolution
The solution to this problem requires actions at two levels:
- An administrator must repair the stopped activity instance manually.
For example, to force complete or force retry the stopped activity instance.
- The reason for the failure must be investigated. In some cases the failure is caused by a modeling error that must be corrected in the model.
Troubleshooting the execution of BPEL processes
Related concepts:
Continue-on-error behavior
Related tasks:
Repairing stopped activities
Repairing stopped activities using the process state view