Controlled shutdown

Stopping an MQ queue manager using the controlled shutdown does not sever any connections immediately, but waits until all connections are closed (this applies to connections formed using the MQSeries® Classes for Java™ in either the bindings or client mode). Any active MQ bridge transmission queue listeners notice that the MQ system is quiescing, and stop with a relevant warning.

Any MQ bridge queues that are active retain a connection to the MQ queue manager until:
  • The connection times-out, after being idle for an idle time-out period, as specified on the client connection bridge object, at which point the broken connection is closed, and the controlled shutdown of the MQ queue manager completes.
  • The MQ bridge queue is told to perform some action, such as put a message to MQ, that attempts to use the broken connection. The putMessage operation fails, the broken connection is closed, and the controlled shutdown of the MQ queue manager completes.

The bridge client-connection object maintains a pool of connections, that are awaiting use. If there is no bridge activity, the pool retains MQ client channel connections until the connection idle time exceeds the idle time-out period (as specified on the client connection object configuration), at which point the channels in the pool are closed.

When the last client channel connection to the MQ queue manager is closed, the MQ controlled shutdown completes.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.