The SbTransport catalog contains messages in the range
BEA381750 - BEA381799. 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-381750
|
Error: Unexpected error happened in the SB Transport at method due to e
|
Description
| An internal error occurred. It is due to either an unrecoverable failure during a configuration update or a runtime error during message processing |
|
Action
| If this error happened during a configuration update, check that your SB transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact technical support. |
|
|
BEA-381751
|
Error: Could not create connection with proxy service s due to m
|
Description
| An error happened while trying to lookup the SB Transport proxy service RMI stubs |
|
Action
| Verify that your JNDI context host, port and credentials are correct. Also check that protocol used by the JNDI context is supported and enabled For instance, IIOP/IIOPS protocols are not supported between WebLogic Server, and HTTP/HTTPS protocols requires HTTP tunnelling |
|
|
BEA-381752
|
Error: Could not invoke proxy service s due to m
|
Description
| An Remote Exception happened while trying to invoke the SB Transport proxy service via RMI |
|
Action
| Check your that network connection, destination server and port are up. Also, check that the remote proxy service still exists |
|
|
BEA-381753
|
Error: Could not generate plan s due to m
|
Description
| An internal error occurred while creating a proxy services with a custom dispatch policy. The deployment plan for this proxy artifact could not be created |
|
Action
| The message body should give you more details about the error. This could be caused by a I/O Exception or because the location of the deployment plan write-protected. |
|
|
BEA-381754
|
Error: Unsupported payload type s
|
Description
| An internal error occurred during the message processing: the payload associated with the message is not supported by the SB Transport |
|
Action
| Contact Technical Support |
|
|
BEA-381755
|
Error: Operation "op" is not valid for this endpoint.
|
Description
| The SB Proxy service is called with operation "op". The operation is either empty, or not defined for the configured WSDL binding. |
|
Action
| Check the client configuration to make sure the operation is set and configured with a valid value. |
|
|
BEA-381756
|
Error: An unexpected error occured initialization DOM support for the transport: e
|
Description
| There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: e |
|
|
BEA-381757
|
Error: An error occured while marshalling the response message: e
|
Description
| An error occured while marshalling the response message. More information should be provided by the following nested exception: e |
|
|
BEA-381758
|
Error: An error occured while transforming the payload: e
|
Description
| The Oracle SOA suite is based on the DOM object model. An error occured while transforming the payload message into a DOM object. More information should be provided by the following nested exception: e |
|
|
BEA-381759
|
Error: An error occured while unmarshalling the request message: e
|
Description
| An error occured while unmarshalling the request message. More information should be provided by the following nested exception: e |
|