hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Karp (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HTTPCLIENT-1104) Add way to check for release of connections back into pool
Date Wed, 22 Jun 2011 16:18:49 GMT
Add way to check for release of connections back into pool
----------------------------------------------------------

                 Key: HTTPCLIENT-1104
                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1104
             Project: HttpComponents HttpClient
          Issue Type: Wish
          Components: HttpClient
            Reporter: John Karp
            Priority: Minor


As the documentation emphasizes, its important to clean up HttpEntities after use, so they
don't tie up the default very small number of connections in the pool.

However, nothing is provided to HttpClient users with the default classes that allows them
to unit test their code to help verify that they are in fact properly releasing the connections
under all circumstances. One way this could be done is for the API to expose the number of
current leased (taken) connections in the pool, which would be connManager.pool.leasedConnections.size()
if not for the necessary fields being protected. If this statistic were published through
the API, user unit tests could check that it is zero when they finish.

A workaround is for the user to subclass both the connection manager and ConnPoolByRoute and
add getter methods. But its kind of a clunky solution, and I think the API should be written
to encourage its users to perform this check.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message