The OSB FLOW Kernel catalog contains messages in the range
BEA2031000 - BEA2031449. Messages in this catalog are part of the
com.bea.alsb.flow.messages Internationalization package and the
com.bea.alsb.flow.messages Localization package.
|
BEA-2031000
|
Error: Split-Join deployment error during activation:\nt
|
Description
| An unexpected error occured while deploying a new/updated Split-Join or undeploying an existing Split-Join. |
|
Action
| Contact technical support |
|
|
BEA-2031001
|
Error: The Activation of Split-Join resources could not be commited because the deployment session has already been closed.
|
Description
| The Activation of Split-Join resources could not be commited because the deployment session has already been closed. This is an invalid state that could be the result of other session (WLS, OSB) related issues. |
|
Action
| The deployment session has not been commited and the server may be in an inconsistent state. If the OSB session has been activated, try to undo and retry the activation. If the problem persists, restarting the server should unlock the sessions. Contact technical support. |
|
|
BEA-2031002
|
Error: Load notifications for Split-Join resources cannot be started because a deployment session is already active.
|
Description
| A deployment session is already active at server startup and a session for the server load notifications cannot be created. |
|
Action
| Contact technical support. |
|
|
BEA-2031003
|
Error: Split-Join deployment error during load notification: msg\nt
|
Description
| An unexpected error occured while deploying a Split-Join during server startup. |
|
Action
| Contact technical support. |
|
|
BEA-2031004
|
Error: Load notifications for Split-Join resources could not be commited because the session has already been closed.
|
Action
| Contact technical support. |
|
|
BEA-2031100
|
Error: Error converting the response message (Split-Join: 'bpel' LINK: 'link' Service: 'svc'): msg\nt
|
Description
| An error occured trying to unmarshall the response of a service invocation. A generic fault will be raise in the Split-Join. |
|
Action
| Turn on transport level debug log to get more information regarding the response message. If the service being invoked is a proxy service, turning on tracing for that service may also provide more information on the message. |
|
|
BEA-2031101
|
Error: Error converting the response fault (Split-Join: 'bpel' LINK: 'link' Service: 'svc'): msg\nt
|
Description
| An error occured trying to unmarshall the fault response of a service invocation. A generic fault will be raise in the Split-Join. |
|
Action
| Turn on transport level debug log to get more information regarding the response message. If the service being invoked is a proxy service, turning on tracing for that service may also provide more information on the message. |
|
|
BEA-2031102
|
Error: Error creating the SOAP Fault from the response fault while calling Split-Join 'bpel': null\nnull
|
Description
| An error occured trying to marshall the fault response into a SOAP Fault. The fault response was processed as if this error did not occur. If an error handler was configured in the calling Split-Join for this fault, and a SOAP Fault variable was defined, then its content will be empty. |
|
|
BEA-2031200
|
Error: Schema validation for ref failed: \nerrors
|
Cause
| The schema has been modified other than by the Split-Join editor |
|
Action
| Please edit Split-Join using the Split-Join editor |
|
|
BEA-2031201
|
Error: Failed to parse schema: error
|
Cause
| The schema has been modified other than by the Split-Join editor |
|
Action
| Please edit Split-Join using the Split-Join editor |
|
|
BEA-2031202
|
Error: Failed to create validation meta data: error
|
Cause
| An unexpected error occurred trying to create meta data from wsdl definitions referenced by Split-Join. |
|
Action
| Contact technical support. |
|
|
BEA-2031203
|
Error: Failed to validate Split-Join: error
|
Cause
| An unexpected error occurred during validation of Split-Join |
|
Action
| Contact technical support. |
|
|
BEA-2031300
|
Error: Variable name is assigned a null value.
|
Description
| The transformation (most probably an assign or replace in that case) did not return any value. |
|
Action
| Turn on tracing to check the data. Check the data expression for the given transformation. An empty result may be due to missing XML elements/attributes in the data, improper use of namespaces... |
|
|
BEA-2031301
|
Error: Variable name is assigned an array of values.
|
Description
| The transformation (most probably an assign or replace in that case) returned more than one value. |
|
Action
| Turn on tracing to check the data. Check the data expression for the given transformation. Such result may happen for example if the selected XML elements/attributes correspond to repeating nodes (XML Schema maxOccurs > 1). |
|
|
BEA-2031310
|
Error: Variable name targeted for replace is not XML.
|
Description
| The variable targeted for replace operation does not hold XML data. |
|
Action
| Check that in the Split-Join resource the variable name is defined by an XML element or comlex type. |
|
|
BEA-2031311
|
Error: Content targeted for replace is not an element or an attribute
|
Description
| Content targeted for replace is not an element or an attribute |
|
Action
| Check the value of the variable that is targeted for replace operation. |
|
|
BEA-2031312
|
Error: An attribute may only be replaced with an attribute
|
Description
| An attribute may only be replaced with an attribute |
|
Action
| Check the value of the variable that is targeted for replace operation. |
|
|
BEA-2031313
|
Error: An element or its contents may only be replaced with elements and simple values
|
Description
| An element or its contents may only be replaced with elements and simple values |
|
Action
| Check the value of the variable that is targeted for replace operation. |
|
|
BEA-2031320
|
Error: A Delete action cannot delete a variable.
|
Action
| Check the XPath expression of the Delete action. The XPath expression should not result in the selection of the variable itself (e.g. ".[0]"). |
|
|
BEA-2031330
|
Error: Variable name targeted for insert is not XML.
|
Description
| The variable targeted for insert operation does not hold XML data. |
|
Action
| Check the value of the variable that is targeted for insert operation. |
|
|
BEA-2031331
|
Error: Content cannot be inserted before/after the variable itself.
|
Description
| The Insert is configured to insert before/after the result of the selection, but the result of the selection is the variable itself. |
|
Action
| Check the XPath expression of the Insert action. The XPath expression should not result in the selection of the variable itself (e.g. ".[0]"). |
|
|
BEA-2031332
|
Error: Failed to insert after.
|
Description
| Inserting the result of this expression after specified XPath resulted in an error. |
|
Action
| Check the value of the variable that is targeted for insert operation. |
|
|
BEA-2031333
|
Error: Cannot insert as a child of an attribute
|
Description
| It is illegal to insert as a child of an attribute |
|
Action
| Check the value of the variable that is targeted for insert operation. |
|
|
BEA-2031334
|
Error: Unable to insert after first child
|
Description
| Unable to insert after first child as there was no child elements of specified XPath expression |
|
Action
| Check the value of the variable that is targeted for insert operation. |
|
|
BEA-2031335
|
Error: Unable to insert after last child
|
Description
| Unable to insert after child element |
|
Action
| Check the value of the variable that is targeted for insert operation. |
|
|
BEA-2031336
|
Error: Only attributes may be inserted next to another attribute
|
Description
| Only attributes may be inserted next to another attribute |
|
Action
| Check the value of the variable that is targeted for insert operation. |
|
|
BEA-2031337
|
Error: Only elements and simple values may be inserted next to or inside of another element
|
Description
| Only elements and simple values may be inserted next to or inside of another element |
|
Action
| Check the value of the variable that is targeted for insert operation. |
|
|
BEA-2031350
|
Error: Parameter at index index in method "method" is assigned an array of values.
|
Description
| The parameter expression returned more than one value for the parameter at index index in method "method". |
|
Action
| Check the data expression for the given parameter. Such result may happen for example if the selected XML elements/attributes correspond to repeating nodes (XML Schema maxOccurs > 1). |
|
|
BEA-2031351
|
Error: Parameter at index index in method "method" is of type XmlObject but the expression resulted in a simple type.
|
Description
| The parameter expression returned a simple type value instead of an XML fragment. |
|
Action
| Check the data expression for the given parameter. An XML fragment is expected but a simple type is returned. |
|
|
BEA-2031352
|
Error: A NumberFormatException was raised for parameter at index index in method "method": msg
|
Description
| A NumberFormatException was raised for parameter at index index in method "method" during the conversion from the simple type result to the expected java type. |
|
Action
| Check the data expression for the given parameter and the schema type of the result. The value returned does not match the expected java type. |
|
|
BEA-2031353
|
Error: Callout to java method "method" resulted in exception: msg
|
Description
| The java method specified in the Java Callout operation was invoked and resulted in an exception. The exception details should be part of the error message. |
|
|
BEA-2031354
|
Error: Security exception while calling to java method "method". Service account: "sacct". message
|
Description
| There was an error while setting up the security context for java callout method. This could happen if there is a problem retrieving the credentials of specified service account. There should be a specific error message that will pinpoint the source of the problem. |
|
|
BEA-2031400
|
Error: No Flow Reference specified.
|
Description
| While trying to create, retrieve or update a Flow Configuration, no reference was specified. |
|
|
BEA-2031401
|
Error: No configuration details specified.
|
Description
| While trying to create or update a Flow Configuration, no configuration details were specified. |
|
|
BEA-2031402
|
Error: No operational values specified.
|
Description
| While trying to update the operational settings for a Flow, no operational settings were specified. |
|
|
BEA-2031403
|
Error: No operational settings query specified.
|
Description
| While trying to return a list of flow refs with a given set of operational values, no operational values were specified. |
|
|
BEA-2031404
|
Error: Expecting ref of type {0} but received ref of type {1}.
|
Description
| A flow ref is expected but received incorrect ref. |
|
Action
| Please check that the passed is ref is correct and is of type flow ref. |
|
|
BEA-2031405
|
Error: An exception occurred trying to suspend the transaction: message.
|
Description
| An unexpected exception occurred while suspending the transaction after invoking an external service. |
|
Action
| Contact technical support. |
|
|
BEA-2031406
|
Warning: There was an exception creating the FlowResult: message
|
Description
| An unexpected exception occurred creating a FlowResult from the OutboundTransportMessageContext. The exception message should provide more details. Processing will continue as though Result Caching is disabled. |
|
Action
| No action required. |
|
|
BEA-2031407
|
Warning: There was an exception processing the FlowResult: message
|
Description
| An unexpected exception occurred processing the FlowResult. The exception message should provide more details. Processing will continue as though Result Caching is disabled. |
|
Action
| No action required. |
|
|
BEA-2031408
|
Warning: There was an exception checking the cache for the request: message
|
Description
| An unexpected exception occurred checking the cache for the request. Processing will continue as though Result Caching is disabled. |
|
Action
| No action required. |
|