The multi-threaded connection manager holds on to connections that have been released, but it does not necessarily close them. Connections are only closed if the server sends a "connection: close" header or if HTTP 1.0 is used.
There are currently two open bugs that may apply to your situation:
<http://issues.apache.org/bugzilla/show_bug.cgi?id=25372> and <http://issues.apache.org/bugzilla/show_bug.cgi?id=27589>
I would also suggest checking the archive for more discussion on this matter.
Mike
On Mar 16, 2004, at 7:31 PM, Eric Bloch wrote:
Hi there,
I've got a question. I'm using the Multithreaded Connection Manager and I know that I'm always calling releaseConnection() on every connection I use. Are there any reports (or possibilities) that releaseConnection() will fail to close an open socket or lose track of is such that I will see socket leaks? This is running against JRE 1.3.1 (on linux).
I have a custy that is seeing leaks WebSphere and at the moment, httpclient is the current suspect since it's one of the few things in the app that causes it to open sockets.
Thanks, -Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
