You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by Michael Becke <mb...@gmail.com> on 2005/04/05 04:42:09 UTC

Re: ExecutorService, Future, and HttpClient with a MultiThreadedHttpConnectionManager

> You should not do that. The API Docs make no promise that this is
> allowed. Especially in a mulithreaded environment this could put a
> connection back to the pool although it is already used by another thead
> again! The consequences would be disasterous. We should address this
> issue in the 4.0 API actually to make a "double free" not suck.

Actually there is no problem in releasing a connection more than once.
 The secondary, tertiary, etc, calls to releaseConnection will get
ignored.

Mike

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