The JEJBTransport catalog contains messages in the range
BEA387301 - BEA387335. Messages in this catalog are part of the
com.bea.wli.sb.transports.jejb Internationalization package and the
com.bea.wli.sb.transports.jejb Localization package.
|
BEA-387301
|
Error: Unexpected error happened in the JEJB 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 JEJB 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-387302
|
Error: Could not create connection with proxy service s due to m
|
Description
| An error happened while trying to lookup the JEJB 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-387303
|
Error: Could not invoke proxy service s due to m
|
Description
| An Remote Exception happened while trying to invoke the JEJB 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-387304
|
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-387305
|
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 JEJB Transport |
|
Action
| Contact Technical Support |
|
|
BEA-387306
|
Error: Method: methodName is not exposed through JEJB inbound service for invocation.
|
Description
| This method is not exposed by the JEJB proxy service for invocation. |
|
Action
| Please check the proxy service configuration. |
|
|
BEA-387307
|
Error: Method: methodName is not exposed through JEJB business service for invocation.
|
Description
| This method is not exposed by the JEJB business service for invocation. |
|
Action
| Please check the business service configuration. |
|
|
BEA-387308
|
Error: Corresponding OSB service is in disabled state.
|
Description
| Corresponding OSB service is in disabled state. |
|
Action
| Please enable the corresponding proxy service. |
|
|
BEA-387309
|
Error: Following Response payload to the inbound JEJB service is not properly formed: message
|
Description
| Response payload to the inbound JEJB service is not properly formed. |
|
Action
| Response message should be modeled as the SOAP message with operation name as the sub-elements. Please refer to the generated wsdl for the message structure. |
|
|
BEA-387310
|
Error: Following Request payload to the outbound JEJB service is not properly formed: message
|
Description
| Request payload to the outbound JEJB service is not properly formed. |
|
Action
| Request message should be modeled as the SOAP message with operation name as the sub-elements. Please refer to the generated wsdl for the message structure. |
|
|
BEA-387311
|
Error: Parameter: paramName with class name: paramClass could not be loaded
|
Description
| Parameter received from the payload could not be loaded. |
|
Action
| Please look at the exception message for the reason. Refer to the generated wsdl for the message structure. |
|
|
BEA-387312
|
Error: No object is registered for ref 'ref'
|
Description
| An attempt to look up an object in Java object repository with the specified reference failed. This may have occurred 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-387313
|
Error: Colocated call is not supported by JEJB transport provider.
|
Description
| Colocated call is not supported by JEJB transport provider. |
|
Action
| Colocated calls are not supported by JEJB transport provider. Please route the pipeline message to JEJB business service. |
|
|
BEA-387314
|
Error: JNDI Provider: refName could not be retrieved due to e
|
Description
| JNDI Provider could not be retrieved due to an unexpected error. |
|
Action
| Please look at error message for the reason. If problem persists, contact technical support. |
|
|
BEA-387315
|
Error: JNDI Provider: refName not found
|
Description
| JNDI Provider does not exists in OSB |
|
Action
| Please make sure that a valid JNDI Provider is configured with the given name. |
|
|
BEA-387316
|
Error: Unexpected error while creating or updating the JEJB Service due to e
|
Description
| Unexpected error while creating or updating the JEJB Service due to e |
|
Action
| Please look at the error for the actual reason. |
|
|
BEA-387317
|
Error: Could not find an existing JNDI provider with one of the following URIs: msg
|
Description
| Could not find an existing JNDI provider with one of the following URIs: msg |
|
Action
| While importing the JEJB service from UDDI, JEJB Transport Provider looks for existing JNDI provider with the same host and port as mentioned in the access point of the imported service. Make sure that a JNDI provider is already created at the time of importing the service. Please refer to the documentation for more details. |
|
|
BEA-387318
|
Error: Java object received from the pipeline message with type: returnTypeInMsg cannot be converted to the expected type: expectedReturnType
|
Description
| Java object received from the pipeline message cannot be converted to the expected type. |
|
Action
| Please check the pipeline logic. Java object received from the pipeline message cannot be converted to the expected type as defined in the ejb interface. |
|