webMethods Adapter Runtime 10.7 | webMethods Adapter Runtime Documentation | webMethods Adapter Runtime User’s Documentation | The Adapter Runtime in a Clustered Environment | Adapter Listener Support in a Cluster | Listener States in a Cluster | Single-Node Listener States
 
Single-Node Listener States
You can change the state of a single-node listener on all nodes in an Integration Server cluster from any node in the cluster. When a single-node listener is enabled, disabled, or suspended on all nodes in the cluster, the action that a particular node takes depends on:
*the selected state change on all nodes
*the listener state on the particular node, that is if the listener thread is running or not
*whether the particular node is the active (primary) node
For example, if a single-node listener has already been suspended on node A, and then on node B you enable the listener on all nodes in the cluster, node A can:
*enable the listener, if node A becomes the active node in the cluster.
*show the listener as enabled without creating a new thread, if another node has already become the active one.
The following table shows what change occurs in the state of a single-node listener on a particular node in the cluster when you enable, disable, or suspend the listener on all nodes.
Listener State on a Particular Node
Enable Listener on All Nodes
Disable Listener on All Nodes
Suspend Listener on All Nodes
Enabled
No action
*Disable the listener if this is the active node
*Show the listener as disabled if this is not the active node. No action
*Suspend the listener if this is the active node
*Show the listener as suspended if this is not the active node. No action
Disabled
*Enable the listener if the node acquires the lock on the shared cache and becomes the active node
*Show the listener as enabled if another node has already become the active node. No action
No action
No action
Suspended
*Enable the listener if the node acquires the lock on the shared cache and becomes the active node
*Show the listener as enabled if another node became the active node. No action
Show the listener as disabled. No action
No action
If a single-node listener is active on a particular node and you try to disable it, another Integration Server node's listener will become active if that listener is in an enabled state. If the listener is in a disabled state on all other Integration Server nodes, those nodes will ignore the disable operation.