Suspending a Process on Uncaught Faults

Suspending a process on an uncaught fault applies to processes running on Process Server.

Use the following techniques to suspend all or individually selected faulting processes on Process Server:

The Suspend on Uncaught Fault setting requires either Full or Persist, process persistence. For information on persistence, see the Process Persistence section within the General Deployment Options topic.

Suspending a process on an uncaught fault applies to processes running on Process Server.

According to the WS-BPEL 2.0 specification, a process with an uncaught fault terminates with a termination handler. However, Process Server allows processes to be suspended when an activity is faulting if the fault does not have a corresponding catch (that is, uncaught). Before completing execution of the activity, the server stops the process so that you can retry or complete the activity.

You can enable this setting in the Process Console. For details, see the Process Console Help.

If desired, you can override the server setting for individual processes. For details, see Making Individual Processes Eligible for Suspension on Uncaught Faults.

Suspending a process on an uncaught fault applies to processes running on Process Server.

On the server, there is a configuration setting to make all processes eligible for suspension on an uncaught fault. However, you can override the server setting in the process deployment descriptor (PDD) file of an individual process. For details, see General Deployment Options.

See also Making all Processes Eligible for Suspension on Uncaught Faults.

For details, see Suspend.