BPEL Dispatch Exceptions ORABPEL 05000 - 05006

BPEL Dispatch Exceptions ORABPEL 05000 - 05006
Dispatch Exceptions 05000 - 05006

ORABPEL-05000
severity: 5
type: error
name: Cannot get dispatcher trace
description: Failed to fetch the dispatcher trace for engine \"{0}\"; the exception reported is: {1}

ORABPEL-05001
severity: 10
type: error
name: Message handler not registered
description: The message handler for class \"{0}\" has not been registered.

ORABPEL-05002
severity: 10
type: error
name: Message handle error
description: An exception occurred while attempting to process the message \"{0}\"; the exception is: {1}

ORABPEL-05003
severity: 10
type: error
name: No message local handler
description: No message local handler has been implemented for the message \"{0}\".

ORABPEL-05004
severity: 10
type: error
name: Dispatcher send error
description: An error occurred while sending a batch message to the dispatch queue. The exception is: {0}

ORABPEL-05005
severity: 10
type: error
name: Cannot send JMS message
description: The process domain was unable to send a message to the JMS queue \"{0}\". The exception reported is: {1}
fix: Please check that the JMS service for the application server has been configured properly.

ORABPEL-05006
severity: 10
type: error
name: Dispatcher schedule error
description: An error occurred while scheduling a batch message with the dispatcher. The exception is: {0}