Hello Neil, On Thu, Feb 24, 2011 at 08:31:26PM +0000, Neil Prockter wrote: > Hello > > I've looked into this further and the trouble is not with tomcat looking > up the client but with tomcat looking up itself. > > changing the haproxy config from > option httpchk GET / > to > option httpchk GET / HTTP/1.1\r\nHost:\ sys-haproxytomcat-test:8080 > > makes the server return quickly
OK so that means that your server might be trying to resolve a default hostname that does not exist. > Needs some more thought but I think I'd like an option to add a fixed > Host header to the request or maybe take the address:port from the > server backend config for that backend server as that can't be specified > in a single check line It's been planned for years, but given it's easy to hack it into the request line as you did, it remained low priority. We'll improve that when we support advanced checks. Thanks for the feedback, Willy
