ol_98173
Feb 23, 2009Nimbostratus
Health Monitor and java broken pipe in Tomcat
Heya All,
I've created health monitor on our LTM:
GET /192.168.0.2:8080/sub/index/?remotecall=info HTTP/1.1\r\nUser-Agent: F5 loadbalancer\r\nHost: 192.168.0.3\r\nConnection: Close\r\n
Note, that ip address in the GET request is intentional, not a mistake!
I've modified User-agent, to be passed to Tomcat as "F5 loadbalancer"
as a result from this HTTP monitor I'm expecting server to return it's IP address, so in this case 192.168.0.2, what works fine in 5 out of 6 times.
And here comes the problem:
every 30 seconds there appears "broken pipe" error in the Tomcat Log. see below:
"ClientAbortException: java.net.SocketException: Broken pipe"
I do not understand Java at all, but ClientAbort Exception sounds like if Client (F5 balancer) aborted the session.
The monitor is setup in order so the node in the pool is monitored every 5 seconds.
Is the monitor setup syntactically ok?