What Happens When You Configure a Deadline for a BPMN Process

Handling Errors 19-3 System exceptions contain an errorInfo attribute of type Any. You can assign any value to this attribute. Because its type is Any this value can belong to any type. Generally you use this attribute to store the cause of the exception or important information for troubleshooting the application. You can only view the list of available system exceptions from the Implementation Properties of an error event. Table 19–1 describes the supported system exceptions. It also specifies the module where the system exception resides and the error events that can use the specified system exception.

19.4 Typical Flow of an Exception

The flow of a system or a business exception depends on where the exception occurred. Exceptions can occur while running the following: ■ a task ■ a subprocess ■ a reusable process

19.4.1 Typical Flow of an Exception Thrown in a Task

The following describes what happens when the BPMN Service Engine runs a task that causes an exception. Table 19–1 System Exceptions System Exception Module Description Error Event AssertFailure Bpel Indicates that the specified assertion failed. Catch, Start BindingFault Bpel Indicates that the preparation of the operation invoked in a flow object failed. For example, the WSD loading failed. You cannot retry the invocation after a BindingFault, recovering from this error generally requires human intervention. Catch, Start InvalidVariables Bpel Indicated that the variables used are not valid. Catch, Start RemoteFault Bpel Indicates that there was a problem invoking a service in a flow object. For example, the remote service returned a SOAP fault. Catch, Start Timeout Soap Indicates that the service exceeded the response time out period. Catch, Start ConflictingReceive Soap Indicates that there are multiple receive activities to respond to the invoked operation. Catch, Start ConflictingRequest Soap Indicates that there are multiple requests on the same partner link for the invoked operation. Catch, Start CorrelationViolation Soap Indicates that the message does not provide the required correlation information. Catch, Start ForcedTermination Soap Indicates the service terminated because a SOAP fault occurred. Catch, End InvalidReply Soap Indicates that the reply does not contain the correlation information required by the corresponding receive. Catch, Start MismatchedAssignmentFailure Soap Indicates the assigned types are incompatible. Catch, Start RepeatedCompensation Soap Specifies that a compensation handler is invoked multiple times. Catch, Start SelectionFailure Soap Indicates there was an error running a selection operation. Catch, Start UninitializedVariable Soap Indicates that the variable you are accessing is not initialized. Catch, Start Rollback Soap Enables the receiver of the exception to rollback the current JTA transaction from within the process flow. Throw, End