commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17968] New: - Allow zero idle objects in GenericObjectPool
Date Thu, 13 Mar 2003 18:54:10 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17968>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17968

Allow zero idle objects in GenericObjectPool

           Summary: Allow zero idle objects in GenericObjectPool
           Product: Commons
           Version: 1.0.1 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Pool
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: scott.finnerty@digitalevergreen.com


We have a situation where we are managing LDAP connections and want
to setup to use a pool to manage the connections.  In one deployment 
of the application, the LDAP server we are using does not allow 
connections to remain idle/open for any length of time, so we need 
to configure the pool to always hand out new connections and destroy 
them when they are returned.  We thought we could do this with a 
maxIdle setting of zero.  However GenericObjectPool will only consider 
destroying an object if the maxIdle is greater than zero - forcing 
you to have at least one idle object in your pool.

The javadoc for GenericObjectPool states that a non-positive value for 
maxIdle implies an unlimited number of idle objects, while the javadoc 
for GenericObjectPool.setMaxIdle(int) states that a negative value for 
maxIdle implies an unlimited number of idle objects.  It seems that 
"non-positive" implies zero or less (<= 0) because that is how the 
code behaves.

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


Mime
View raw message