Oracle Traffic Director Deployment Of Config Change Hangs After Disabling A TCP Listener Listening On VIP Of A Failover Group
(Doc ID 2092244.1)
Last updated on JUNE 20, 2024
Applies to:
Oracle Traffic Director - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
A TCP listener is configured to listen on a virtual ip (VIP) that is configured for a failover group. After disabling the listener via the admin console and then subsequently deploying the change, the console hangs for 1 or 2 minutes and then gives an error that says the deployment on one node (<HOSTNAME1>) is successful and the deployment on the other node (<HOSTNAME2> ) failed due to the node being unreachable.
The admin server server.log has:
The issue is reproducible even without using the admin console for deployment of the config change. It can be reproduced using the following sequence:
1. Increase the number of acceptor threads for a listener to a higher value (e.g 96).
2. Start the instance with the listener enabled.
3. Manually edit server.xml to disable the listener (e.g: <enabled>false</enabled> )
4. Run /bin/reconfig on the instance that doesn't have VIP running
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |