The ALSB Kernel catalog contains messages in the range
BEA382000 - BEA382499. Messages in this catalog are part of the
com.bea.wli.sb.messages Internationalization package and the
com.bea.wli.sb.messages Localization package.
|
BEA-382000
|
Error: General runtime error: message
|
Description
| A general runtime error has occured in ALSB pipeline runtime while processing the message. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382001
|
Error: Context variable names must be non-null and have non-zero length
|
Description
| A runtime error has occured in ALSB pipeline runtime while processing the message. Message context variable names must be non-null and have non-zero length |
|
Action
| Check your pipeline configuration to make sure all variable names are properly configured and have non-zero length |
|
|
BEA-382002
|
Error: Router runtime cache has not been initialized on this node!
|
Description
| An unexpected error has occurred in during the initialization of ALSB pipeline runtime while processing the request message for specified proxy service. |
|
Action
| Contact technical support |
|
|
BEA-382003
|
Error: Unknown error while processing message for service service
|
Description
| An error has occurred in ALSB pipeline runtime while processing the request message for specified proxy service. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382004
|
Error: Failed to process request message for service serviceName: t
|
Description
| An error has occurred in ALSB pipeline runtime while processing the request message for specified proxy service. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382005
|
Error: Failed to process response message for service serviceName: t
|
Description
| An error has occurred in ALSB pipeline runtime while processing the response message for specified proxy service. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382006
|
Error: No object is registered for ref 'ref'
|
Description
| An error has occurred in ALSB pipeline runtime while processing the response message for specified proxy service due to an attempt to look up an object in Java object repository with the specified reference. This may have occured to due a previously executed pipeline action that deleted the object with the corresponding reference. |
|
Action
| Check the pipeline message flow configuration to make sure there is no pipeline action that deletes the object with the specified reference that executes prior to this error |
|
|
BEA-382007
|
Error: Failed to start timer timerName: t
|
Description
| There was an unexpected error while collecting statistics in ALSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382008
|
Error: Failed to lookup counter counterName
|
Description
| There was an unexpected error while collecting statistics in ALSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382009
|
Error: Failed to increment counter counterName: t
|
Description
| There was an unexpected error while collecting statistics in ALSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382010
|
Error: Failed to stop timer timerName: t
|
Description
| There was an unexpected error while collecting statistics in ALSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382011
|
Debug: serviceName: Non-cataloged debug message: message
|
Description
| This is a log message with debug severity logged by ALSB pipeline runtime for diagnostic purposes |
|
|
BEA-382013
|
Error: The configurations for the proxy service is in flux.
|
Description
| The processing of the message has failed in ALSB runtime due to the fact that the configurations for the proxy service is in flux. This proxy is unable to send an outbound message to service "service" until the configuration stabilizes. |
|
Action
| Wait until the configuration of ALSB server stabilizes and retry sending the request. |
|
|
BEA-382014
|
Error: The configurations for the proxy and target services are in flux. This proxy is unable to route to service "service" until the configuration stabilizes.
|
Description
| The processing of the message has failed in ALSB runtime due to the fact that the configurations for the proxy and target services are in flux. This proxy is unable to send an outbound message to service "service" until the configuration stabilizes. |
|
Action
| Wait until the configuration of ALSB server stabilizes and retry sending the request. |
|
|
BEA-382015
|
Error: Cannot create RouterContext for non-proxy services: serviceName
|
Description
| There was an internal error while initializing the ALSB pipeline runtime state for given service. Only proxy service can process inbound messages |
|
Action
| Contact technical support |
|
|
BEA-382016
|
Error: Failed to instantiate router for service serviceName: t
|
Description
| There was an error while initializing the ALSB pipeline runtime state for given proxy service. There should be a specific message that describes specific cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-382017
|
Error: Failed to find runtime object for this service: serviceName
|
Description
| There was an unexpected error while initializing the ALSB pipeline runtime state for given service. |
|
Action
| Contact technical support |
|
|
BEA-382018
|
Error: Unable to generate runtime for router configuration: config
|
Description
| This is a diagnostic error message that is logged with error severity in the event ALSB pipeline runtime fails to initialize its state. The message will contain various bits of information that will help in the analysis of the underlying cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382019
|
Error: Failed to parse configuration into typed XmlObject: config
|
Description
| There was an error while initializing ALSB pipeline runtime state for a given service. The error occurred while parsing the saved configuration for service message flow |
|
Action
| Contact technical support |
|
|
BEA-382020
|
Error: Failed to register the stage action actionName: t
|
Description
| There was an error during the initialization and/or registration of single pipeline action actionName. This may happen due to misconfigured installation of ALSB product |
|
Action
| Contact technical support |
|
|
BEA-382021
|
Error: Failed to register the stage-action application appName: t
|
Description
| There was an error during the initialization and/or registration of a set of pipeline actions contained in an application file appName. This may happen due to misconfigured installation of ALSB product |
|
Action
| Contact technical support |
|
|
BEA-382022
|
Error: Failed to load factory class: factory
|
Description
| There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to misconfigured installation of ALSB product |
|
Action
| Contact technical support |
|
|
BEA-382023
|
Error: Failed to instantiate instance of action factory: factory
|
Description
| There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to misconfigured installation of ALSB product |
|
Action
| Contact technical support |
|
|
BEA-382024
|
Error: Failed to instantiate instance of action factory (constructor may not be public): factory
|
Description
| There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to misconfigured installation of ALSB product |
|
Action
| Contact technical support |
|
|
BEA-382028
|
Error: Failed to load WSDL binding information for service
|
Description
| There was an unexpected error during the processing of the message by ALSB pipeline runtime. The error happened while trying to load WSDL binding information for proxy service. |
|
Action
| Check configuration of proxy service service and contact technical support |
|
|
BEA-382029
|
Error: Failed to create WS-I compliance checker
|
Description
| There was an unexpected error during the processing of the message by ALSB pipeline runtime. The error happened during initialization of component that checks for WS-I compliance. |
|
Action
| Contact technical support |
|
|
BEA-382030
|
Error: Failure while unmarshalling message: message
|
Description
| There was an error parsing request or rensponse payload. E.g. the request payload may have improperly formatted multipart/related data which will lead to an error trying to unmarshal message attachments. There will be an error message that will point to specific cause of the error |
|
Action
| Look at the specific error message and examine the payload to see why ALSB fails to unmarshall its contents properly. |
|
|
BEA-382031
|
Error: WS-I Compliance failure (rule): message
|
Description
| The body of request or response message does not conform to WS-I basic profile due to stated reason. This could happen when receiving request messages by ALSB proxy services or response messages from business services enabled for WS-I compliance. |
|
Action
| Look at the specific error message and examine the payload to see why the body of the message fails WS-I compliance check |
|
|
BEA-382032
|
Error: The message must be an instance of: qname
|
Description
| There was an error parsing the contents of request or response message due to the fact that the payload was expected to contain a valid SOAP envelope but did not. This can happen for when a SOAP (Any SOAP or WDSL-based ALSB proxy receives a request message that does not contain a valid SOAP envelope |
|
Action
| Examine the payload to make sure it contains valid SOAP envelope |
|
|
BEA-382033
|
Error: A soap:Envelope must contain a soap:Body
|
Description
| There was an error parsing the contents of request or response message due to the fact that the payload was expected to contain a valid SOAP Body within SOAP Envelope but did not. This can happen for when a SOAP (Any SOAP or WDSL-based ALSB proxy receives a request message that does not contain a valid SOAP Body element in its envelope |
|
Action
| Examine the payload to make sure it contains valid SOAP Body element |
|
|
BEA-382034
|
Error: Expected SOAP 1.1 Envelope
|
Description
| There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Envelope element was missing. |
|
Action
| Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body |
|
|
BEA-382035
|
Error: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Header element was missing.
|
Action
| Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body |
|
|
BEA-382036
|
Error: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Body element was missing.
|
Action
| Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body |
|
|
BEA-382037
|
Error: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Envelope element was missing.
|
Action
| Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body |
|
|
BEA-382038
|
Error: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Header element was missing.
|
Action
| Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body |
|
|
BEA-382039
|
Error: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Body element was missing.
|
Action
| Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body |
|
|
BEA-382040
|
Error: Failed to set the value of context variable "variable". Value must be an instance of type.
|
Description
| There was an error assigning a value to specified message context variable. There are certain message context variables, e.g. $outbound, $attachments, $fault that have a pre-defined structure (see online ALSB documentation for details) and any value assigned to them is expected to be in certain format |
|
Action
| Use ALSB Log action to verify that the value being assigned to the variable is in fact in expected format |
|
|
BEA-382041
|
Error: Failed to set the value of context variable "variable". Variable is read-only.
|
Description
| There was an error assigning a value to specified message context variable. There are certain message context variables, e.g $operation that one cannot assign values to and thus they are considered read-only. |
|
Action
| Check ALSB on-line documentation to make sure that the variable whose value is being changed is not considered a read-only variable. |
|
|
BEA-382042
|
Error: Failed to set the value of context variable "variable". message
|
Description
| There was an error assigning a value to specified message context variable. This may happen when trying to assign non-XML values to message context variables that expect XML content (e.g. $fault). |
|
Action
| Use ALSB Log action to verify that the value being assigned to the variable is in fact in expected format |
|
|
BEA-382043
|
Error: Failed to update the value of context variable "variableName": message
|
Description
| There was an error assigning or updating a value of a specified message context variable. This may happen when the value being assigned does not conform to specified format for a system variable (e.g. setting $outbound to null) or updating a read-only portion of a variable (e.g. changing service element of $inbound) message context variable |
|
Action
| Use ALSB Log action to verify that the value being assigned to the variable is in fact in expected format. Also check ALSB on-line documentation to make sure that the part of the variable that you are changing is not considered read-only. |
|
|
BEA-382045
|
Error: Failed to initialize the value of context variable "variableName": message
|
Description
| There was an unexpected error while initializing one of the system variables. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382046
|
Error: Failed to marshall the value of context variable "variableName" to XML: message
|
Description
| There was an error retrieving the XML representaiton of the value of a system context variable, e.g. request or response meta-data for $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382047
|
Error: Processor must be in INACTIVE state
|
Description
| There was an internal error in ALSB pipeline runtime while processing the inbound request by a proxy service. The state of ALSB pipeline was not expected |
|
Action
| Contact technical support |
|
|
BEA-382048
|
Error: Processor must be in RESPONSE or ERROR state
|
Description
| There was an internal error in ALSB pipeline runtime while processing the inbound request by a proxy service. The state of ALSB pipeline was not expected |
|
Action
| Contact technical support |
|
|
BEA-382100
|
Error: Failure in binding-layer while processing inbound request for service service: message
|
Description
| There was an error in ALSB pipeline runtime while processing the inbound request by a proxy service. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382101
|
Error: Failure in binding-layer while preparing inbound response for service service: message
|
Description
| There was an error in ALSB pipeline runtime while preparing the inbound response for a proxy service. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382102
|
Error: Failure in binding-layer while preparing outbound request for service service: message
|
Description
| There was an error in ALSB pipeline runtime while preparing the outbound request for a business service. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382103
|
Error: Failure in binding-layer while processing outbound response for service service: message
|
Description
| There was an error in ALSB pipeline runtime while processing the outbound response from a business service. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382104
|
Error: Failed to prepare request metadata for service service: message
|
Description
| There was an error in ALSB pipeline runtime while processing the request metadata for either $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382105
|
Error: Failed to prepare response metadata for service service: message
|
Description
| There was an error in ALSB pipeline runtime while processing the response metadata for either $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382106
|
Error: XQuery expression for input parameter resulted in null
|
Description
| The configured XQuery expression the result of which is used for input parameter to XSLT transformation resulted in null. |
|
Action
| Please check the configured expression to make sure it results in non-null value. One can use Log action to log the result of any XQuery expression. |
|
|
BEA-382107
|
Error: No value could be bound to variable: varName
|
Description
| The configured XQuery expression the result of which is used for named input variable to XSLT transformation resulted in null. |
|
Action
| Please check the configured expression to make sure it results in non-null value. One can use Log action to log the result of any XQuery expression. |
|
|
BEA-382108
|
Error: XPath can only be executed against XML or MFL content
|
Description
| The configured XPath expression refers to a message contents variable or other expression whose content is not XML. XPath can only be executed against XML or MFL content |
|
Action
| Please check the value the configured expression to make sure that it refers to valid XML content. One can use Log action to log the result of any expression including message context variables. |
|
|
BEA-382109
|
Error: Node execute method is not supported in optimized Xslt transform
|
Description
| An unexpected error has occurred in ALSB pipeline runtime while processing an action that uses XSLT transformation. |
|
Action
| Contact technical support |
|
|
BEA-382150
|
Error: Failure while dispatching request to service service: message
|
Description
| There was an unexpected error in ALSB pipeline runtime while performing an outbound request for either routing, publish or service callout action. There should be a specific error message that will point to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-382151
|
Error: Nothing is known about service service
|
Description
| There was an unexpected error retrieving configuration details for specified service service. |
|
Action
| Use ALSB console to check that the service in question is properly configured |
|
|
BEA-382152
|
Error: Message-context property "doOutboundWss" is set to true but proxy "proxy" is a passive intermediary: passive intermediary proxies do not support outbound web service security (target service: "target")
|
Description
| Message-context property "doOutboundWss" is set to true but proxy "proxy" is a passive intermediary: passive intermediary proxies do not support outbound web service security (target service: "target") |
|
Action
| Use ALSB console to check the configuration of the the service in question and make sure the specified message context property is set correctly. |
|
|
BEA-382153
|
Error: Cannot delete system variable "variableName" from context
|
Description
| An attempt to delete a system variable from the message context failed because there are a number of system variables that cannot be deleted, such as $inbound and $outbound. |
|
Action
| Check ALSB online documentation on whether a given system variable can be deleted from the message context. |
|
