RE: PoolingClientConnectionManager Using Non-standard HTTP Port Question

[Chris Larsen]

Final follow up. The ES instance I was running defaulted to listening on
IPv6. When I toggled it to listen over the IPv4 address, the connection pool
worked beautifully. So it could be an issue with IPv6 from my machine
(Windows).