WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

States of the WebSphere MQ link and its channels

This topic describes the various states of the WebSphere MQ link and its sender and receiver channels, on a service integration bus.

State of WebSphere MQ link WebSphere MQ link sender channel WebSphere MQ link receiver channel
INACTIVE Same as STOPPED for the WebSphere MQ link sender. If the administrator requests that the channel go into target state STOPPED it will transition into the STOPPED state. Similarly, an administrator starting the channel will cause it to transition into STANDBY state. No network connection exists between the application server and the queue manager. If a WebSphere MQ sender channel's attempts to establish a connection should succeed, it will become possible for messages to flow from the queue manager to the messaging engine. In this case the receiver channel will transition into RUNNING state.
STARTING A transitional state. The channel should successfully pass through this into BINDING state with no intervention. A transitional state. The channel should successfully pass through this into BINDING state with no intervention.
BINDING A transitional state. The channel should successfully pass through this into RUNNING state with no intervention. The channel may transition into STOPPING state if a problem occurs. A transitional state. The channel should successfully pass through this into RUNNING state with no intervention. The channel may transition into STOPPING state if a problem occurs.
INITIALIZING A transitional state. The channel should successfully pass through this into STARTING state with no intervention. A transitional state. The channel should successfully pass through this into STARTING state with no intervention.
RETRYING A network connection to the queue manager has been lost. Whilst in this state the channel is attempting to reestablish the connection. If the retry intervals are exhausted without successfully establishing the connection then the channel transitions into STOPPED state. If a connection is successfully reestablished, the channel enters INITIALIZING state. Not applicable to receiver channel.
STANDBY When in this state, the sender channel is not network-connected to its WebSphere MQ counterpart receiver channel. It is waiting for a message to send before attempting to establish a connection. When a message arrives for transmission, the channel will transition into STARTING state and start the process of attempting to establish a network connection. The administrator may command the channel to transition into either INACTIVE or STOPPED state from this state. Not applicable to receiver channel.
RUNNING In this state a network connection has been established between application server and queue manager. Messages destined for the queue manager will be transmitted. Either attempting to stop the channel using the administrative console, or the loss of the network connection will cause transition into the STOPPING state. Network connection established between application server and queue manager. Messages destined for the messaging engine will be received. Attempting to stop the channel, or the loss of the network connection will cause a transition into STOPPING state.
STOPPING A transitional state. The channel should transition into either RETRYING state or STOPPED state without intervention. If the channel has been placed in STOPPING state by the administrative request to become INACTIVE then it will transition into the STANDBY state. If the channel has been placed in this state by administrator request to stop, it will transition into the STOPPED state. If the channel has been placed in this state by a broken network connection it will transition into the RETRYING state, assuming that it has non-zero retry intervals or is otherwise STOPPED. A transitional state. The channel will transition from this state into STOPPED without intervention.
STOPPED No network connection exists between the application server and the queue manager. Messages destined for the queue manager will not be transmitted. To transition from this state requires the administrator to start the channel, this will place it in STANDBY state. No network connection exists between the application server and the queue manager. Any attempt by a sender channel in the WebSphere MQ network to establish a connection will be rejected. Messages destined for the messaging engine will not be received. Administrator action is required to move the channel out of this state. Starting the channel will move it into INACTIVE state.

For information about the states of the channels in a WebSphere MQ network refer to the Intercommunications book available at the WebSphere MQ publications site


Reference topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\ref\rjc0020_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)