Forum Discussion
Pool Health Monitor Generates Lots of Close_wait
Hi All,
Im having an issue with my LTM VS, for an ATM application, where the pool health monitor is generating lots of close_wait connections to the Unix server pool (which are not closed) causing the application to eventually hang after a period of time. Is there any way to monitor a service/port of the application on server without making a TCP connection? It seems that the ATM application (which is asynchronous connection) is not closing the health monitor probes generated from F5 LTM. Appreciate for any recommendation / help?
Thanks! Ramil
2 Replies
- nitass
Employee
is tcp-half-open monitor helpful?
TCP Half Open Monitors the associated service by sending a TCP SYN packet to the service. As soon as the monitor receives the SYN-ACK packet, the monitor marks the service as up.Manual Chapter: Monitors Settings Reference
http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-monitors-reference-11-2-0/3.html - Ramil_Ancajas_1
Nimbostratus
Cool! I tried it and it works!
Thanks Nitass you are a star!
Ramil
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com