I have noticed that when a ConnectionTimeoutException is thrown, HttpConnection doesn't seem to release the connection. If a lot of timeouts are encountered, this eventually results in a hang when no more connections are available.
Instead, the connection seems to be correctly released to the MultiThreadedHttpConnectionManager if a read timeout occurs,ie a java.net.SocketTimeoutException is thrown.
Below is the relevant part of my log..
Thanks
10633 DEBUG [MainCheck1] httpclient.HttpMethodDirector - Execute loop try 1
10633 DEBUG [MainCheck1] httpclient.MultiThreadedHttpConnectionManager - enter HttpConnectionManager.getConnectionWithTimeout(HostConfiguration, long)
10633 DEBUG [MainCheck1] httpclient.MultiThreadedHttpConnectionManager - HttpConnectionManager.getConnection: config=HostConfiguration[host=www.museums.reading.ac.uk, protocol=http:80, port=80],timeout = 0
10633 DEBUG [MainCheck1] httpclient.MultiThreadedHttpConnectionManager - enter HttpConnectionManager.ConnectionPool.getHostPool(HostConfiguration)
10633 DEBUG [MainCheck1] httpclient.MultiThreadedHttpConnectionManager - enter HttpConnectionManager.ConnectionPool.getHostPool(HostConfiguration)
10634 DEBUG [MainCheck1] httpclient.MultiThreadedHttpConnectionManager - Allocating new connection, hostConfig=HostConfiguration[host=www.museums.reading.ac.uk, protocol=http:80, port=80]
10634 DEBUG [MainCheck1] httpclient.HttpConnection - HttpConnection.setSoTimeout(3000)
10634 DEBUG [MainCheck1] httpclient.HttpConnection - enter HttpConnection.open()
13644 WARN [MainCheck1] httpclient.HttpConnection - The host www.museums.reading.ac.uk:80 (or pro
xy null:-1) did not accept the connection within timeout of 3000 milliseconds
here no call to HttpConnection.releaseConnection() is performed!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
