Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient Project" <httpclient-dev@jakarta.apache.org>
From: bugzilla@apache.org
To: httpclient-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 39014]  - HTTP Client 3.0 doesn't close sockets
In-Reply-To: <bug-39014-13697@http.issues.apache.org/bugzilla/>
Message-Id: <20060317152734.D993F6ACA9@ajax.apache.org>
Date: Fri, 17 Mar 2006 15:27:34 +0000 (GMT)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39014>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39014


------- Additional Comments From odi@odi.ch  2006-03-17 15:27 -------
HttpClient fully supports persistent connections as defined per section 8.1 of
RFC 2616. The connection pool implementation is responsbile for closing physical
connections when they become stale.

I guess your application does not profit of connection pooling as it never hits
the same host twice. So open connections keep accumulating in the pool. Thus you
should disable the pooling by the measures outlined earlier. A different very
simple solution is to use the MultithreadedConnectionManager which supports
setting a limit via its setMaxTotalConnections method. If none of those
suggestions meet your needs you can always implement your own connection manager.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org