Support Article
Listeners and agents are not moved to another node when quiesced
SA-27134
Summary
When a node is quiesced and the requestors passivated and moved to another available node in the cluster, the Listeners and Agents running on the quiesced node are shut down, but not automatically moved/enabled on another node in the cluster to continue processing. Instead, they are shut down and unavailable in the application if they were only running on that one node - which is always the case for Legacy agents and those not configured to run on more than that one node in the cluster.
Error Messages
Not Applicable
Steps to Reproduce
- Configure at least two nodes and HA properly.
- Add an Email Listener to node A but not to node B
- Start agents on node A but not on node B
- Quiesce node A using SMA and make sure both email listeners and all previoiusly running agents are enabled and now running on Node B
Root Cause
This issue was determined to be a product enhancement request.
Resolution
This issue was determined to be a product enhancement request.
Published September 9, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.