Process Developer

Back Next

BPEL Standard Faults

The table below specifies the standard faults defined within the WS-BPEL specification. All these faults are named within the WS-BPEL namespace with a standard prefix

bpel:

corresponding to the following URI:

http://docs.oasis-open.org/wsbpel/2.0/process/executable

Fault Name	Description
ambiguousReceive	Thrown when a business process instance simultaneously enables two or more IMAs for the same partnerLink, portType, or operation but different correlation sets, and the correlations of multiple of these activities match an incoming request message
completionConditionFailure	Thrown if upon completion of a directly enclosed <scope> activity within <forEach> activity, it can be determined that the completion condition can never be true
conflictingReceive	Thrown when more than one inbound message activity is enabled simultaneously for the same partner link, port type, operation, and correlation sets.
conflictingRequest	Thrown when more than one inbound message activity is open for the same partner link, operation, and message exchange
correlationViolation	Thrown when the contents of the messages that are processed in an <invoke> , <receive> , <reply> , <onMessage> , or <onEvent> do not match specified correlation information.
invalidBranchCondition	Thrown if the integer value used in the <branches> completion condition of <forEach> is larger than the number of directly enclosed <scope> activities.
invalidExpressionValue	Thrown when an expression used within a WS-BPEL construct (except <assign> ) returns an invalid value with respect to the expected XML Schema type.
invalidVariables	Thrown when an XML Schema validation (implicit or explicit) of a variable value fails
joinFailure	Thrown when the join condition of an activity evaluates to false and the value of the suppresJoinFailure attribute is yes
mismatchedAssignmentFailure	Thrown when incompatible types or incompatible XML infoset structure are encountered in an <assign> activity.
missingReply	Thrown when an inbound message activity executed, and the process instance or scope instance reaches the end of its execution without a corresponding <reply> activity being executed.
missingRequest	Thrown when a <reply> activity cannot be associated with an open inbound message activity by matching the partner link, operation, and message exchange tuple.
scopeInitializationFailure	Thrown if there is a 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	Thrown when a selection operation performed either in a function such as bpel:getVariableProperty or in an assignment, encounters an error.
subLanguageExecutionFault	Thrown when the execution of an expression results in an unhandled fault either in an expression language or query language.
uninitializedPartnerRole	Thrown when an <invoke> or <assign> activity references a partner link whose partnerRole endpoint reference is not initialized.
uninitializedVariable	Thrown when 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	Thrown when 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	Thrown when the transformation source provided in a bpel:doXslTransform function call was not legal.
xsltStylesheetNotFound	Thrown when the named style sheet in a bpel:doXslTransform function call was not found.