The OSB FLOW Transport catalog contains messages in the range
BEA2030500 - BEA2030999. Messages in this catalog are part of the
com.bea.alsb.flow.transport Internationalization package and the
com.bea.alsb.flow.transport Localization package.
|
BEA-2030500
|
Error: Fatal error during initialization of Split-Join AppListener. Root cause: e
|
Description
| Without correct initialization of Split-Join AppListener requests to Split-Join business services will not work. |
|
Cause
| Received exception during initialization of Split-Join AppListener |
|
Action
| Please make sure product installation is complete. Restart server. If error persists, contact support. |
|
|
BEA-2030600
|
Error: Error during conversion of fault response to source for Split-Join "ref". Root cause: e
|
Description
| An attempt will be made to return a fault response with a server error of type http://www.bea.com/alsb/flow/faults:responseProcessingFault. |
|
Cause
| Message converter could not transform the fault message. The fault message is potentially invalid. The exception should provide more details about the actual error. |
|
Action
| Make sure the fault message format is correct and conforms to the style/use specified in the wsdl associated with flow. Please correct the fault message and try again. |
|
|
BEA-2030601
|
Error: Error during conversion of response to source for Split-Join "ref". Root cause: e
|
Description
| An attempt will be made to return a fault response with a server error of type http://www.bea.com/alsb/flow/faults:responseProcessingFault. |
|
Cause
| Message converter could not transform the response message. The response message is potentially invalid. The exception should provide more details about the actual error. |
|
Action
| Make sure the response message format is correct and conforms to the style/use specified in the wsdl associated with Split-Join. Please correct the response message and try again. |
|
|
BEA-2030602
|
Error: Unable to dispatch fault response for "flow" due to error creating response metadata. Root cause: e
|
Cause
| This is an unexpected error. This should not normally happen. |
|
Action
| Please make sure product installation is complete. Restart the server. Make sure there are no errors during server startup. Make sure Split-Join is deployed correctly. If error persists, contact support. |
|
|
BEA-2030603
|
Error: Error during conversion of default server fault response to source for Split-Join "ref". Root cause: e
|
Cause
| Message converter could not transform the fault message. The fault message is potentially invalid. The exception should provide more details about the actual error. |
|
Action
| Make sure the fault message format is correct and conforms to the style/use specified in the wsdl associated with Split-Join. Please correct the fault message and try again. |
|
|
BEA-2030604
|
Error: Unable to dispatch response for "splitJoin" due to error creating response metadata. Root cause: e
|
Cause
| This is an unexpected error. This should not normally happen. |
|
Action
| Please make sure product installation is complete. Restart the server. Make sure there are no errors during server startup. Make sure Split-Join is deployed correctly. If error persists, contact support. |
|
|
BEA-2030605
|
Error: Error during scheduling response for "splitJoin". Root cause: e
|
Cause
| The exception should provide the root cause for the error |
|
Action
| Please correct the error before trying again. |
|
|
BEA-2030606
|
Error: Error parsing request metadata for Split-Join. Request metadata XML must be an instance of "type". Root cause: "rootCause"
|
Cause
| Request metadata is not of the expected type |
|
Action
| Make sure the request passed in has request metadata that conforms to the schema of Split-Join request metadata. |
|
|
BEA-2030607
|
Error: Unexpected error: Binding in business service "bizSvc" is incorrect. Found "abstract XML" binding type, but expecting "SOAP" binding type.
|
Cause
| Found "abstract XML" binding type but expecting "SOAP" binding type. |
|
Action
| Regenerate the transport typed business service for Split-Join. If error persists please contact support. |
|
|
BEA-2030700
|
Error: Unable to invoke Split-Join as the request is received from sender "senderType" that is not supported. Only a transport-type business service of type Split-Join can invoke a Split-Join.
|
Cause
| Request for Split-Join received from an unsupported sender type |
|
Action
| Make sure the Split-Join end point is associated with a business service that is transport-typed and whose id is Split-Join. |
|
|
BEA-2030701
|
Error: Unable to invoke Split-Join as the Split-Join end point could not be created successfully as it is null.
|
Cause
| Sender is not configured correctly with the Split-Join end point. |
|
Action
| Make sure the Split-Join end point is associated with a business service that is transport-typed and whose id is Split-Join. Make sure the installation is complete and there are no errors on server startup. |
|
|
BEA-2030702
|
Error: Unexpected error, the Split-Join transport configuration descriptor cannot be loaded. Root cause: "string"
|
Description
| Unexpected errors will be seen if a business service based on Split-Join is invoked. |
|
Cause
| The exception should provide more details about the error. Make sure the configuration file for Split-Join transport is well-formed and conforms to the schema |
|
Action
| Make sure product installation is complete and there are no errors during server startup. If error persists, please contact support. |
|