Error handling for HttpHostConnectionException is incomplete. When the HttpClient looses connection to the JD's Web Server, the above exception is thrown. There is an explicit
catch() to deal with it but all it does now is just log the problem once. So what happens in this scenario is that a thread fails over and over again.
What should happen here is that a single thread should attempt connection recovery sleeping for awhile (default=60sec) and try again. Other threads (if scaleout > 1), should block doing nothing until a thread doing the retry succeeds.