commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Feig (JIRA)" <j...@apache.org>
Subject [jira] Created: (POOL-130) GenericObjectPool.Evictor creates new objects although exactly minIdle objects are idle
Date Mon, 06 Oct 2008 14:51:44 GMT
GenericObjectPool.Evictor creates new objects although exactly minIdle objects are idle
---------------------------------------------------------------------------------------

                 Key: POOL-130
                 URL: https://issues.apache.org/jira/browse/POOL-130
             Project: Commons Pool
          Issue Type: Bug
    Affects Versions: 1.4, 1.2
            Reporter: Torsten Feig


When you 
- create a GenericObjectPool with these parameters: maxActive=100, maxIdle=100, minIdle=10,
timeBetweenEvictionRunsMillis=360000 (1h), minEvictableIdleTimeMillis=30000 (5min)
- preload the 10 minIdle objects (10x borrowObject() + returnObject)
you have a pool with 10 idle objects.

Then every 1h the evictor destroys the 10 idle objects and creates 10 new ones. Why? After
all, creating and tearing down pool objects is likely to be expensive. So why destroy the
old objects when they exactly represent the minIdle objects? I don't see any need for this.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message