BPEL Standard Faults
These faults are defined within the WS-BPEL specification. All standard fault names are qualified with the standard WS-BPEL namespace.
| This fault is thrown | When |
|---|---|
| ambiguousReceive | A business process instance simultaneously enables two or more inbound message activities (IMAs) for the same partnerLink, portType, and operation but different correlation sets, and the correlations of multiple of these activities match an incoming request message. |
| completionConditionFailure | A directly enclosed Scope activity within a forEach activity completes and it is determined that the completion condition can never be true. |
| conflictingReceive | More than one inbound message activity (IMA) is enabled simultaneously for the same partner link, port type, operation and correlation sets. |
| conflictingRequest | More than one inbound message activity (IMA) is open for the same partner link, operation and message exchange. |
| correlationViolation | The messages contents processed in an Invoke, Receive, Reply, onMessage, or onEvent don't match the specified correlation information. |
| invalidBranchCondition | The integer value used in the Branches completion condition of a forEach is larger than the number of directly enclosed Scope activities. |
| invalidExpressionValue | An expression used within a WS-BPEL construct (except an Assign) returns an invalid value with respect to the expected XML Schema type. |
| invalidVariables | An XML Schema validation (implicit or explicit) of a variable value fails. |
| joinFailure | The join condition of an activity evaluates to false and the value of the suppresJoinFailure attribute is yes. |
| mismatchedAssignmentFailure | Incompatible types or incompatible XML infoset structure are encountered in an Assign activity. |
| missingReply | An IMA is executed and the Process or Scope instance reaches the end of its execution without a corresponding Reply activity executing. |
| missingRequest | A Reply activity cannot be associated with an open inbound message activity by matching the partner link, operation and message exchange. |
| scopeInitializationFailure | There is any problem creating any of the objects defined as part of Scope initialization. This fault is always caught by the parent Scope of the faulted Scope. |
| selectionFailure | A selection operation performed either in a function such as bpel:getVariableProperty, or in an assignment, encounters an error. |
| subLanguageExecutionFault | The execution of an expression results in an unhandled fault in an expression language or query language. |
| uninitializedPartnerRole | An Invoke or Assign activity references a partner link whose partnerRole endpoint reference is not initialized. |
| uninitializedVariable | There is an attempt to access the value of an uninitialized variable, or in the case of a message type variable, one of its uninitialized parts. |
| unsupportedReference | A WS-BPEL implementation fails to interpret the combination of the reference-scheme attribute and the content element OR just the content element alone. |
| xsltInvalidSource | The transformation source provided in a bpel:doXslTransform function call is not legal. |
| xsltStylesheetNotFound | The named style sheet in a bpel:doXslTransform function call is not found. |
More information