ASYNCEXCEPTION

This property determines whether WebSphere® MQ classes for JMS informs an ExceptionListener only when a connection is broken, or when any exception occurs asynchronously to a JMS API call. This applies to all Connections created from this ConnectionFactory that have an ExceptionListener registered.

Applicable objects

ConnectionFactory, QueueConnectionFactory, TopicConnectionFactory, XAConnectionFactory, XAQueueConnectionFactory, XATopicConnectionFactory

JMS administration tool long name: ASYNCEXCEPTION

JMS administration tool short name: AEX

Programmatic access

Setters/Getters

  • MQConnectionFactory.setAsyncExceptions()
  • MQConnectionFactory.getAsyncExceptions()

Values

ASYNC_EXCEPTIONS_ALL

Any exception detected asynchronously, outside the scope of a synchronous API call, and all connection broken exceptions are sent to the ExceptionListener.

Environment Value
JMS Administration Tool ALL
Programmatic WMQCONSTANTS.ASYNC_EXCEPTIONS_ALL = -1
WebSphere MQ Explorer All
ASYNC_EXCEPTIONS_CONNECTIONBROKEN

Only exceptions indicating a broken connection are sent to the ExceptionListener. Any other exceptions occurring during asynchronous processing are not reported to the ExceptionListener, and hence the application is not informed of these exceptions. [V7.5.0.8 Jun 2017]This is the default value from IBM® WebSphere MQ Version 7.5.0, Fix Pack 8 (see JMS: Exception listener changes in Version 7.5).

Environment Value
JMS Administration Tool CONNECTIONBROKEN
Programmatic WMQCONSTANTS.ASYNC_EXCEPTIONS_CONNECTIONBROKEN = 1
WebSphere MQ Explorer Connection Broken
The following additional constant is defined: [V7.5.0.8 Jun 2017]
  • From Version 7.5.0, Fix Pack 8: WMQCONSTANTS.ASYNC_EXCEPTIONS_DEFAULT = ASYNC_EXCEPTIONS_CONNECTIONBROKEN
  • Before Version 7.5.0, Fix Pack 8: WMQCONSTANTS.ASYNC_EXCEPTIONS_DEFAULT = ASYNC_EXCEPTIONS_ALL