|
BEA-2032000
|
Error: Error during invocation of "process" for event "eventID" of type "eventType".
|
Cause
| There are several reasons for the invocation to fail. The exception must provide details to help identify the reason for the failure. |
|
Action
| Fix the artifact based on the exception. If the exception is not clear contact support. |
|
|
BEA-2032001
|
Error: Fatal error: Unable to invoke "process" for event "eventID" of type "eventType" as "process" does not exist.
|
Cause
| The artifact invoked does not exist. This is probably due to the fact that there were errors during deployment or the session used to deploy is not activated yet. |
|
Action
| Make sure the invoked artifact is correct, deployed correctly and the session used to deploy the artifact is activated without errors. |
|
|
BEA-2032002
|
Error: Received unknown message exchange "msgExchangeType" on reply. Reply will be ignored.
|
Description
| Reply expects message exchange of type "RequestResponseMessageExchange". However, received an unknown message exchange. Hence, reply will be ignored |
|
Cause
| Unable to dispatch reply as an unknown message exchange is received. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032003
|
Error: Neither output nor fault is set on response for message exchange "msgExchangeDetail" for blocking request with key "key". Reply will be ignored.
|
Cause
| Either output or fault must be set on a response. However, neither is set for the message exchange. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032004
|
Error: Callback listener is missing for message exchange "msgExchangeDetail" for non-blocking request with key "key". Reply will be ignored.
|
Cause
| Callback listener that is used to dispatch the reply for non-blocking requests is missing. Hence, the reply can not be dispatched. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032005
|
Error: Neither output nor fault is set on response for message exchange "msgExchangeDetail" for non-blocking request with key "key". Reply will be ignored.
|
Cause
| Either output or fault must be set on a response. However, neither is set for the message exchange. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032006
|
Error: Unknown data type "type" found for data in dispatcher cache for request with message exchange "msgExchangeDetail", with key "key". Reply will be ignored.
|
Cause
| Type of data found in dispatcher cache is unknown. Hence, reply can not be dispatched. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032007
|
Error: Timeout for event "timeoutData" can not be dispatched as the key (used to look up request entry in the dispatcher cache)is null. Timeout will be ignored.
|
Cause
| This error could be due to a system defect in garbage collection or unique id generation. This could also be due to data corruption. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032008
|
Error: Unknown data type "dataType" found for data, with key "key", in the dispatcher cache when trying to dispatch timeout event for a non-blocking request. Timeout will be ignored.
|
Cause
| System defect or data corruption is the cause of this failure. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032009
|
Error: Error Dispatching the Event: unexpected error. - message.
|
Cause
| The exception message should describe the cause. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032010
|
Error: Error Dispatching the Event: the service-ref is unsupported. - message.
|
Cause
| The exception message should describe the cause. |
|
Action
| This is an unexpected error. Please contact support. |
|
|
BEA-2032100
|
Error: Scheduler can not dispatch request to engine as the process "ref" is not found. Request will be ignored.
|
Cause
| The process is no longer deployed and active. Either the process is undeployed or session activation failed during process deployed as the session had errors. |
|
Action
| Make sure the process is deployed correctly. If error persists, please contact support. |
|
|
BEA-2032101
|
Error: Scheduler can not dispatch request to engine for process "ref" as the message exchange is null. Request will be ignored.
|
Cause
| Message exchange is null. |
|
Action
| This is an unexpected error. Please contact support. |
|