Class JmsConnectionErrorHandler

  • All Implemented Interfaces:
    ComponentLifecycle, ConnectionErrorHandler, javax.jms.ExceptionListener

    public class JmsConnectionErrorHandler
    extends JmsConnectionErrorHandlerImpl
    implements javax.jms.ExceptionListener
    Standard implementation of ConnectionErrorHandler which implements ExceptionListener.

    In the adapter configuration file this class is aliased as jms-connection-error-handler which is the preferred alternative to the fully qualified classname when building your configuration.

    • Constructor Detail

      • JmsConnectionErrorHandler

        public JmsConnectionErrorHandler()
      • JmsConnectionErrorHandler

        public JmsConnectionErrorHandler​(java.lang.Boolean singleExecution)
    • Method Detail

      • stop

        public void stop()
        Description copied from interface: ComponentLifecycle
        Stop the component

        A stopped component is not expected to be ready to process messages. In the case of AdaptrisMessageConsumer, calling stop will pause message delivery. Throwing a RuntimeException may cause unintended consequences

        Specified by:
        stop in interface ComponentLifecycle
      • close

        public void close()
        Description copied from interface: ComponentLifecycle
        Closes the component.

        A closed component should release any connections it uses, etc. and clean up completely. Throwing a RuntimeException may cause unintended consequences

        Specified by:
        close in interface ComponentLifecycle
      • onException

        public void onException​(javax.jms.JMSException e)
        Specified by:
        onException in interface javax.jms.ExceptionListener
      • getSingleExecution

        public java.lang.Boolean getSingleExecution()
        Returns:
        the singleExecution value.
      • setSingleExecution

        public void setSingleExecution​(java.lang.Boolean b)
        Ignore multiple invocations of the ExceptionListener.onException(JMSException) method.

        There is no JMS specification guarantee that a provider will not issue multiple calls to ExceptionListener.onException(JMSException) in short order. In some cases this does happen, which can cause subequent problems based on timing around when the connections re-initialise themselves.

        Parameters:
        b - whether or not to filter multiple executions; defaults to true if not specified.