The WliSbTransport catalog contains messages in the range
BEA382000 - BEA382050. Messages in this catalog are part of the
com.bea.wli.sb.transports.soa Internationalization package and the
com.bea.wli.sb.transports.soa Localization package.
|
BEA-382000
|
Error: Unexpected error happened in the Transport at method due to e
|
Description
| An internal error occurred. |
|
|
BEA-382001
|
Error: URI "uri" is not valid for this endpoint.
|
Description
| The SOA-DIRECT business service is called with URI "uri". The URI is either empty, or does not conform to the URI format for the SOA-DIRECT transport. |
|
|
BEA-382002
|
Error: The callback marker URI is not a valid URI.
|
Description
| The SOA-DIRECT business service is invoked with the callback marker URI, which is not a valid URI at runtime. |
|
Action
| there are different ways the URI was set as the callback marker URI: - dynamically overriden in the pipeline - the business service is configured with the marker URI and the pipeline logic did not override it Check the pipeline and/or SOAP headers and make sure the correct URI is configured. |
|
|
BEA-382003
|
Error: An unexpetced error occured while reading either the MessageID and/or RelatesTo headers: e
|
Description
| An unexpetced error occured while reading either the MessageID and/or RelatesTo headers. More information should be provided by the following nested exception: e |
|
|
BEA-382004
|
Error: An unexpetced error occured while setting/updating the ReplyTo address: e
|
Description
| An unexpected error occured while setting/updating the ReplyTo address. More information should be provided by the following nested exception: e |
|
|
BEA-382005
|
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 |
|
|
BEA-382006
|
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-382007
|
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-382008
|
Error: Operation "op" is not valid for this endpoint.
|
Description
| The SOA-DIRECT business service is called with operation "op". The operation is either empty, or not defined for the configured WSDL binding. |
|
Action
| Check the configuration of the pipeline to make sure the operation is set and configured with a valid value. |
|
|
BEA-382009
|
Error: Could not invoke proxy service s due to m
|
Description
| An Remote Exception happened while trying to invoke the SOA-DIRECT 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-382010
|
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-382011
|
Error: An error occured while marshalling the Business fault: e
|
Description
| An error occured while marshalling the Business fault. More information should be provided by the following nested exception: e |
|
|
BEA-382012
|
Error: An unexpected error occured while setting/updating the FaultTo address: e
|
Description
| An unexpetced error occured while setting/updating the FaultTo address. More information should be provided by the following nested exception: e |
|
|
BEA-382013
|
Error: An unexpetced error occured while checking whether a transaction is running: e
|
Description
| An unexpected error occured while checking whether a transaction is running. More information should be provided by the following nested exception: e |
|
|
BEA-382014
|
Error: No callback address for WSA ReplyTo or FaultTo header
|
Description
| There is no callback address for the WSA callback header: neither the endpoint defines a physical address nor the header defines a callback address. |
|
Action
| Set a physical callback address in the transport configuration for this header, or manually add it in the pipeline |
|