Skip Headers

# JMS Processing Exceptions (18001 - 18004)

Previous

Next

`JMSProcessingException` is a run-time exception that is raised when processing JMS messages.

Format

    EXCEPTION [TOPLINK – error code]: Exception name
    EXCEPTION DESCRIPTION: Message

JMS Processing Exception

    EXCEPTION [TOPLINK – 18001]: oracle.toplink.exceptions.JMSProcessingException
    EXCEPTION DESCRIPTION: Error while processing incomming JMS message.

18001: DEFAULT
  Cause: Failed to process the incoming JMS message.
  Action: See the generated exception for the root cause.

18002: NO_TOPIC_SET
  Cause: `JMSClusteringService` failed to start because the `Topic` created in the JMS service for the interconnection of sessions is `null`.
  Action: Ensure that the `Topic` created in the JMS service for the interconnection of sessions is set in the `JMSClusteringService`.

18003: MDB_ERROR_LOOKUP_SESSION_NAME_ENV
  Cause: Failure in looking up the session's name defined it the `env-entry` element of the message-driven bean.
  Action: Verify the correctness of the `env-entry` element definition of the Message Driven Bean.

18004: MDB_FOUND_NO_SESSION
  Cause: The message-driven bean (MDB) cannot find the session.
  Action: Ensure that the session that this MDB's `getSession()` method returns is not `null` session.