The WliSbTransports catalog contains messages in the range
BEA381901 - BEA381949. Messages in this catalog are part of the
com.bea.wli.sb.transports Internationalization package and the
com.bea.wli.sb.transports Localization package.
|
BEA-381901
|
Error: Exception in method, e
|
Description
| An unexpected general purpose exception has occurred in OSB MQ transport. There should be an error message that points to cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-381902
|
Warning: method received a message without a Correlation Id; dropping message...
|
Description
| The MQ cleanup thread has picked up a message from configured MQ response destination that did not have expected CorrelationID message property. As a result, the response message was dropped. |
|
Action
| Make sure that the back end MQ business service is properly functioning (e.g. that the CorrelationID is being echoed when responding). |
|
|
BEA-381903
|
Warning: Response message with Correlation ID correlationId could not be correlated; the Unrecognized Message URI was not configured, hence the message will be dropped
|
Cause
| The MQ cleanup thread has picked up a message from configured MQ response destination that did not have expected CorrelationID message property. Such messages are routed to the Unrecognized Message URI; if the URI is not configured, the messages are dropped. |
|
Action
| Please configure Unrecognized Message URI on the (MQ) Business Service configuration. |
|
|
BEA-381904
|
Error: Unexpected type of message received: messageType
|
Description
| A non Text or Bytes message was received by MQ proxy service or as a response to MQ business service. OSB MQ transport only supports Text and Bytes messages. |
|
Action
| Make sure only MQ Text or Bytes messages are being sent to OSB JMS proxy or business services. |
|
|
BEA-381905
|
Error: The URIs for request and response may not be equal
|
Description
| In the configuration for the MQ proxy service the request and response URIs are the same. Such conguration is not legal as it will most likely result in an infinite loop and request/response processing. |
|
Action
| Make sure that request and response URIs have different values in MQ proxy service configuration |
|
|
BEA-381906
|
Error: URI uri for this proxy service is already used by another proxy service: other
|
Description
| Two or more MQ proxy services are using the same URI. The operation cannot be completed because only a single MQ proxy is allowed to receive messages from a given MQ destination. |
|
Action
| Make sure that the given MQ proxy is the only one that is configured with the URI in question. |
|
|
BEA-381907
|
Error: The URI uristr is not valid
|
Description
| One or more of the URIs configured for MQ service is not in the format exptected by OSB. The expected format is mq://host:port?conn=MyOSBProject/MyMQConnectionResource |
|
Action
| Make sure that the URI string conforms to the expected format |
|
|
BEA-381908
|
Error: Failed to lookup MQ Connection Resource name
|
Description
| Failure when trying to lookup MQ Connection Resource specified in the URI of the service. |
|
Cause
| The MQ connection resource specified in the URI may not exist. |
|
Action
| Please ensure that the MQ connection resource specified in the URI exists. |
|
|
BEA-381909
|
Error: Service binding is incompatible with transport configuration (response message type)
|
Description
| The configuration of the MQ service was not compatible with the declared service binding type. For example, a messaging service with non-'None' response type has to have a response destination configured in MQ transport configuration. |
|
Action
| Make sure that the MQ transport configuration of the service is consistent with declared service binding type. |
|
|
BEA-381910
|
Info: No response payload to send on Inbound MQ Async-Sync endpoint
|
Description
| This is an informational message to alert the user that an empty response payload is being sent as a response to MQ proxy with response |
|
Action
| If this is expected behavior, no action is required. Otherwise one can use various pipeline actions to examine and set the body of the response message to be sent. |
|
|
BEA-381911
|
Error: Endpoint: epName activation failed.
|
Description
| Service endpoint could not be activated due to an unexpected exception. There may be an error message that points to the cause of the problem. |
|
Action
| Error message may point to the cause of the problem. |
|
|
BEA-381912
|
Error: Endpoint: epName could not be resumed.
|
Description
| Service endpoint could not be resumed due to an unexpected exception. There may be an error message that points to the cause of the problem. |
|
Action
| Error message may point to the cause of the problem. |
|
|
BEA-381913
|
Error: Error occured while polling the resource for Endpoint: epName. Polling will be stopped.
|
Description
| A fatal error has occured when trying to poll the MQ queue specified in the URI of the service. |
|
Action
| The error message may point to the cause of the problem. |
|
|
BEA-381914
|
Warning: Missing MQ library com.ibm.mq.jar; please add the missing library to the classpath.
|
Description
| This error will occur if the MQ native library (com.ibm.mq.jar) is missing on the classpath. |
|
Cause
| This error will occur if the MQ native library (com.ibm.mq.jar) is missing on the classpath. |
|
Action
| Please add the MQ library (com.ibm.mq.jar) to the classpath |
|
|
BEA-381915
|
Error: Error occured while polling the resource for response; Endpoint: epName. Polling will be stopped.
|
Description
| A fatal error has occured when trying to poll the MQ queue specified in the response URI of the service. |
|
Action
| The error message may point to the cause of the problem. |
|
|
BEA-381916
|
Error: Error occured when connecting to MQ: message
|
Description
| An error has occured when trying to connect to the MQ server; please check the MQ reason code associated with the error for more details |
|
Action
| Please check the MQ reason code associated with the error for more details |
|
|
BEA-381917
|
Warning: MQ Transport could not be registered due to message
|
Description
| An error has occured when trying the deploy the MQ transport. |
|
Action
| The error message may contain more details regarding the cause of the problem. |
|
|
BEA-381918
|
Warning: Failed to receive response, within the configured timeout, for request message with id messageId
|
Description
| While invoking a MQ business service, a response to a MQ request did not arrive before specified timeout expired. |
|
Action
| Check that back-end MQ business service is functioning properly and increase the timeout value if necessary |
|
|
BEA-381919
|
Error: The MQ Connection Resource ref in URI uri does not exist
|
Action
| Make sure that the MQ connection resource referenced in the URI exists. |
|
|
BEA-381920
|
Error: The Unrecognized Response URI should not be the same as Response URI for the service
|
Description
| In the configuration for the MQ business service the Unrecognized Response URI and Response URI are the same. Such conguration is not legal as it will most likely result in an infinite loop and request/response processing. |
|
Action
| Make sure that Unrecognized Response URI and Response URI have different values in MQ business service configuration |
|
|
BEA-381921
|
Error: Error trying to access queue queue
|
Description
| OSB could not connect to the configured queue on MQ Server. |
|
Action
| Please check if the queue exists on the configured MQ Server. |
|
|
BEA-381922
|
Error: Error trying to send message to ref; queue queue not available.
|
Description
| OSB could not send message because queue in not available. |
|
Action
| Please check if the queue exists on the configured MQ Server. |
|