mod_proxy_hcheck should be aware of BalancerMember's connectiontimeout parameter and should timeout based on it.

When connectiontimeout parameter is given to BalancerMember directive like the following, mod_proxy_hcheck is not aware of the connectiontimeout parameter. Therefore, in case that the network is unreachable, the worker for health-check does not timeout in connectiontimeout seconds even though the worker for real HTTP request to the same backend timeouts in connectiontimeout seconds. mod_proxy_hcheck should be aware of BalancerMember's connectiontimeout parameter and should timeout based on it.

<VirtualHost *:80>
  ...(snip)...
  ProxyPass /A balancer://webapps/A
</VirtualHost>

<Proxy balancer://webapps>
  BalancerMember http://<host1_ipaddress>:<host1_port> route=jvm1 loadfactor=10 connectiontimeout=15 hcmethod=TCP hcinterval=5 hcpasses=2 hcfails=3
  BalancerMember http://<host2_ipaddress>:<host2_port> route=jvm2 loadfactor=10 connectiontimeout=15 hcmethod=TCP hcinterval=5 hcpasses=2 hcfails=3
  ProxySet stickysession=JSESSIONID|jsessionid
</Proxy>