The WliSbTransports catalog contains messages in the range
BEA381600 - BEA381649. 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-381601
|
Error: Error encountered while putting the message in the queue for the service endpoint epName: e
|
Description
| Message may not be processed as there was an unexpected error while putting the message in the task queue. There should be an error message that points to the cause of the problem. |
|
Action
| Error message may point to the cause of the problem. |
|
|
BEA-381602
|
Error: Error encountered while polling the resource for the service endpoint epName: e
|
Description
| Unexpected exception happened at the time of polling the external resource. There should be an error message that points to the cause of the problem. |
|
Action
| Error message may point to the cause of the problem. |
|
|
BEA-381603
|
Error: Error occured while polling the resource for the service endpoint epName. Polling will be stopped: e
|
Description
| An unexpected exception occured at the time of polling the external resource. There should be an error message that points to the cause of the problem. This is a fatal error and may stop the polling of external resource. |
|
Action
| Reactivate the service or restart the server. |
|
|
BEA-381604
|
Error: Error while initializing the Transport Provider providerName: e
|
Description
| An unexpected exception occured while initializing the Transport Provider. There may be an error message that points to the cause of the problem. |
|
Action
| There may be an error message that points to the cause of the problem. |
|
|
BEA-381605
|
Warning: Error occured for the service endpoint: e
|
Action
| Contact technical support. |
|
|
BEA-381606
|
Error: Error encountered while executing the task from PolledMessageListener MDB.
|
Description
| An unexpected exception occured while passing the message to the pipeline. There should be an error message that points to the cause of the problem. |
|
Cause
| There should be an error message that points to the cause of the problem. |
|
|
BEA-381607
|
Error: Error encountered while parsing the transport provider configuration file filePath: e
|
Action
| Contact techincal support. |
|
|
BEA-381608
|
Warning: JMS Error encountered while putting the message in the queue for the service endpoint serviceName: e.
|
Description
| JMS Error encountered while putting the message in the queue. Failure will be handled by the service. For ex. if its a File Transport Provider service then file will be moved to the error directory. |
|
|
BEA-381609
|
Warning: Naming Service error encountered while doing the lookup for the JMS connection factory or the queue. Failure occured for the service serviceName: e
|
Description
| JMS Error encountered while doing the lookup for the JMS connection factory or the queue. Failure will be handled by the service. For ex. if its a File Transport Provider service then file will be moved to the error directory. |
|
|
BEA-381610
|
Warning: Response Type is not expected for the transport provider: providerId
|
Description
| Response type should be none for the given transport provider if the service is configured with mixed binding type . |
|
Action
| Make sure that response message type is none if the service is configured with mixed binding type. |
|
|
BEA-381611
|
Error: Poller target server should be specified in case of cluster domain.
|
Description
| Poller target server should be specified in case of cluster domain. |
|
Action
| Make sure that the File proxy configuration has one of the managed servers as poller target server if it is running in the cluster. |
|
|
BEA-381612
|
Error: Poller target server should belong to one of the managed servers in the OSB cluster domain.
|
Description
| Poller target server should belong to one of the managed servers in the OSB cluster domain. |
|
Action
| Make sure that the File proxy configuration has one of the managed servers as poller target server if it is running in the cluster. |
|
|
BEA-381613
|
Error: Service endpoint epName activation failed: e
|
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-381614
|
Error: Service endpoint epName could not be resumed: e
|
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. |
|