A fault was not handled by any 'catch' or 'catchAll' element. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, fault-information = cc....cc, activity-name = dd....dd

aa....aa: Business process definition name
bb....bb: Business process definition version
cc....cc: Fault information
dd....dd: Name of activity in which the fault occurred

Description

A fault response from a service component, throw activity, or validate activity, or the CSBUserException exception thrown by a Java class was not processed by catch and catch-all defined in the dialog box allocated for fault processing.

(O)

Check and revise the business process definition from the following viewpoints or check and revise the service component or Java class:

• Is the fault processing for catch or catch-all missing from the definition in the invoke service activity, invoke java activity, or scope activity?
• Does the service component executed in the invoke service activity return a fault defined in the business process definition and service adapter definition?
  To revise the service component executed in the invoke service activity, compare the WSDL provided by the service component and the format of the fault message returned by the service component.
  To revise the Java class executed by the invoke java activity, check and, if necessary, revise the information specified in the CSBUserException exception thrown by the Java class.
  To revise the throw activity or validate activity, check and, if necessary, revise the format of the fault message for the specified variable.