What does the MQ queue error 2009 mean?

What does the MQ queue error 2009 mean?

Reason code 2009 indicates that the connection to the MQ queue manager is no longer valid, usually due to a network or firewall issue. Reason code 2019 errors will occur when invalid connections remain in the connection pool after the reason code 2009 error occurs.

What is the MQ reason code for 2019 in WebSphere?

An application running in WebSphere® Application Server may receive failures when sending messages to, or receiving messages from, a WebSphere MQ or Embedded Messaging queue. The MQ reason code associated with the error is 2019.

What is the cause of the jmsexception 2019?

Note that the cause of the JMSException can be determined by the MQ reason code that appears in the backtrace. In this case, it is reason code 2019. Reason code 2019 usually occurs after a connection broken error (reason code 2009) occurs.

What is MQ reason code 2009 (mqrc_connection_broken)?

The IBM WebSphere MQ Reason Code 2009 (MQRC_CONNECTION_BROKEN) may occur when an application tries to connect to a WebSphere MQ queue manager. Often this occurs when the Application Server tries to use an MQ connection is QCF pool.

How to determine the cause of a jmsexception?

Note that the cause of the JMSException can be determined by the MQ reason code that appears in the backtrace. In this case, it is reason code 2019. Reason code 2019 usually occurs after a connection broken error (reason code 2009) occurs. You would see a JMSException with reason code 2009 preceding reason code 2019 in the SystemOut.log.

Why is my queue manager connection broken?

The connection may be broken for a number of different reasons; the 2009 reason code indicates that something prevented a successful connection to the Queue Manager. The most common causes for 2009 are the following: 1. A firewall has terminated the connection.

  • October 6, 2022