WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the default messaging provider > Interoperate with a WebSphere MQ network > Use WebSphere MQ links to connect a bus to a WebSphere MQ network > Administer an existing WebSphere MQ link > Stopping a WebSphere MQ link

Stopping the receiver channel on a WebSphere MQ link

We can stop the receiver channel on a WebSphere MQ link while leaving the link itself running.

If you stop the receiver channel on a WebSphere MQ link, communication with the target WebSphere MQ network on that channel will cease for both point-to-point messaging and publishing and subscribing. Messages will be held at their transmission locations.

You might want to warn the administrator of the WebSphere MQ network that you are about to stop the channel. If you stop a receiver channel, messages sent to the WebSphere MQ link engine are not received.

If a WebSphere MQ sender channel is started while an MQ link receiver channel is stopped, the request fails with an error indicating the receiver channel is not available.

For more information about stopped states of the WebSphere MQ link and its channels, see States of the WebSphere MQ link and its channels.

  1. Start the dmgr console.
  2. In the navigation pane, click Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional properties] WebSphere MQ links -> link_name -> [Additional Properties] Receiver channel.

  3. Select the check box next to the channel to stop.
  4. In the Stop mode list, select Quiesce or Force.
  5. In the Target state list, select Inactive or Stopped.

  6. Click Stop.


Results

Stopping a receiver channel stops all the receiver channel connections for that receiver. The resultant state of the receiver channel, and the sender channel in the WebSphere MQ network with which it is communicating, depends on the options you choose:

Stop modes. The table contains information about the target states and the corresponding stop modes for stopping the receiver channel on a WebSphere MQ link. There are two target states such as inactive and stopped, and there are two stop modes such as quiesce and force. The rows in the table represent the two target states, and the two stop modes are described in the two columns for each of the target state.

Target state Quiesce stop mode Force stop mode
Inactive The receiver channel moves to the stopping state and the data flow to the WebSphere MQ sender channel stops. When the WebSphere MQ sender channel next tries to communicate with the receiver channel the WebSphere MQ sender channel enters a state of retrying. The receiver channel then becomes inactive. The retrying WebSphere MQ sender channel then reestablishes a session with the receiver channel, and both channels become running. The receiver channel immediately becomes inactive. When the WebSphere MQ sender channel next tries to communicate with the receiver channel, the WebSphere MQ sender channel enters a state of retrying. The retrying WebSphere MQ sender channel then reestablishes a session with the receiver channel, and both channels become running.
Stopped The receiver channel moves to the stopping state and the data flow to the WebSphere MQ sender channel stops. When the WebSphere MQ sender channel next tries to communicate with the receiver channel the WebSphere MQ sender channel enters a state of retrying. The receiver channel then becomes stopped, so preventing the WebSphere MQ sender channel from reestablishing a session. The WebSphere MQ sender channel itself then becomes stopped. The receiver channel immediately becomes stopped. When the WebSphere MQ sender channel next tries to communicate with the receiver channel, the WebSphere MQ sender channel enters a state of retrying, and then becomes stopped itself.


+

Search Tips   |   Advanced Search