I haven't used HttpClient 3.1 for a very long time, but...

[snip]
INFO | jvm 1 | 2010/03/01 10:14:56 | 2010/03/01 10:14:56:968 MEZ [DEBUG] HttpMethodDirector - Closing the connection. INFO | jvm 1 | 2010/03/01 10:14:56 | 2010/03/01 10:14:56:968 MEZ [DEBUG] HttpMethodDirector - Method retry handler returned false. Automatic recovery will not be attempted
This looks like you don't have retries enabled, or the retry count might be too low.

INFO | jvm 1 | 2010/03/01 10:14:56 | 2010/03/01 10:14:56:968 MEZ [DEBUG] HttpConnection - Releasing connection back to connection manager. INFO | jvm 1 | 2010/03/01 10:14:56 | 2010/03/01 10:14:56:968 MEZ [DEBUG] HttpConnection - Releasing connection back to connection manager.

INFO | jvm 1 | 2010/03/01 10:10:41 | 2010/03/01 10:10:41:125 MEZ [DEBUG] HttpConnection - Releasing connection back to connection manager.

as far as I know I don't get any exception.

After this errors I restart apache and all works like expected.
During the restart I get a timeout. (also part from the logs)

When you say you get a timeout, do you mean that the log file has an exception in it? And so this is what you'd expect?

My question is: why do I not get an exception

and further can someone look into the logs and give me a hint. The question is: is this an expect behaviour when the webserver don't work correct? When not: how can I isolate the problem at my httpclient lib usage? Does any have any similare problems and or experience with a problem like this?

Don't know if something is swallowing an exception - normally I'd expect to see a connection timeout, for example.

I would try logging again, this time at the trace level, to see if more context is returned. And a wire log for the failure case, so you'd see exactly what's coming back from the server.

-- Ken

--------------------------------------------
Ken Krugler
+1 530-210-6378
http://bixolabs.com
e l a s t i c   w e b   m i n i n g





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to