Class: JMSException


Interface used to receive asynchronously delivered exceptions. JMS exceptions may be due to a number of different reasons and/or caused by different APIs:
  • connection exceptions caused by timeouts while communicating with the JMS broker;
  • argument exceptions caused by passing invalid arguments or specifying inexistent destination names;
  • authorization exceptions thrown by a server-side hook;
  • etc.
See JMSException#getErrorCode for a list on known exception error codes.

new JMSException()

This method is not meant to be used directly. Creates a JMSException with the specified reason and error code.

Method Summary

Gets the error code.
Gets the exception message.

Method Detail

getErrorCode() → {String}

Gets the error code. The following error codes are used for specific error conditions on the JMS Extender:
  • "JMSEXT_CONNECTION_DISABLED": the JMS Connector is not enabled; when an exception with this error code is reported, contact your system administrator;
  • "JMSEXT_INVALID_CONNECTOR_NAME": the JMS Connector specified while connecting does not exist;
  • "JMSEXT_CONNECTION_NOT_AVAILABLE": the JMS Connector is not able to obtain a connection to the JMS broker; under normal conditions this exception should never be reported;
  • "JMSEXT_CONNECTION_TIMED_OUT": the connection to the JMS broker is temporarily not available; when this exception is reported, a previously requested operation could not be completed, the JMS Extender will reconnect as soon as possible and the operation can subsequently be retried;
  • "JMSEXT_INVALID_ACK_MODE": an invalid ack mode has been requested;
  • "JMSEXT_DUPS_OK_NOT_AVAILABLE": a session with ack mode DUPS_OK has been requested, but the JMS Connector and the underlying JMS broker do not support it;
  • "JMSEXT_INDIVIDUAL_ACK_NOT_AVAILABLE": a session with ack mode INDIVIDUAL_ACK has been requested, but the JMS Connector and the underlying JMS broker do not support it.

getMessage() → {String}

Gets the exception message.