We recommend that before you stop a WebSphere MQ queue manager, you issue a stop administration message to all the WebSphere MQ queue-manager-proxy bridge objects. This stops the WebSphere MQ Everyplace network from trying to use the WebSphere MQ queue manager and possibly interfering with the shutdown of the WebSphere MQ queue manager. (This can also be achieved by issuing a single stop administration message to the MQebridges object.)
If you choose not to stop the WebSphere MQ queue-manager-proxy bridge object before you shut the WebSphere MQ queue manager, the behavior of the WebSphere MQ shutdown and the WebSphere MQ-bridge depends on the type of WebSphere MQ queue manager shutdown you choose, immediate shutdown or controlled shutdown.
Stopping a WebSphere MQ queue manager using immediate shutdown severs any connections that the WebSphere MQ-bridge has to the WebSphere MQ queue manager (this applies to connections formed using the MQSeries Classes for Java in either the bindings or client mode). The WebSphere MQ system shuts down as normal.
This causes all the WebSphere MQ-bridge transmission queue listeners to stop immediately, each one warning that it has shut down due to the WebSphere MQ queue manager stop.
Any WebSphere MQ-bridge queues that are active retain a (broken) connection to the WebSphere MQ queue manager until:
When an WebSphere MQ-bridge queue has no connection, the next operation on that queue causes a new connection to be obtained. If the WebSphere MQ queue manager is not available, the operation on the queue fails synchronously. If the WebSphere MQ queue manager has been restarted after the shutdown, and a queue operation, such as putMessage, acts on the bridge queue, then a new connection to the active WebSphere MQ queue manager is established, and the operation executes as expected.
Stopping a WebSphere 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 WebSphere MQ-bridge transmission queue listeners notice that the WebSphere MQ system is quiescing, and stop with a relevant warning.
Any WebSphere MQ-bridge queues that are active retain a connection to the WebSphere MQ queue manager until:
The bridge client-connection object maintains a pool of connections, that are awaiting use. If there is no bridge activity, the pool retains WebSphere MQ client connections until the connection idle time exceeds the idle time-out period (as specified on the client connection object configuration), at which point the connections in the pool are closed.
When the last client connection to the WebSphere MQ queue manager is closed, the WebSphere MQ controlled shutdown completes.