commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (POOL-265) Evictor automatically destroys object after some time, even when conditions are not met
Date Wed, 31 Dec 2014 16:18:14 GMT

     [ https://issues.apache.org/jira/browse/POOL-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Phil Steitz closed POOL-265.
----------------------------

> Evictor automatically destroys object after some time, even when conditions are not met
> ---------------------------------------------------------------------------------------
>
>                 Key: POOL-265
>                 URL: https://issues.apache.org/jira/browse/POOL-265
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: Mac OS 10.8.2
>            Reporter: garima
>
> We have created generic object pool using following configuration. But evictor which
is supposed to run in every 2.5 min and check for min idle connections and destroy objects
(other than min idle connections i.e 2) which have been idle from last 5 mins is not working
as expected. Evictor starts destroying objects(min idle instances) in every 15 minutes, which
is absolutely wrong as per documentation and should not be happened. Can you please look into
this issue?
> 	INX_POOL2 = new GenericObjectPool<InteractionServerProtocol>(new InxCacheFactory());
> 			INX_POOL2.setMinIdle(2);
> 			INX_POOL2.setNumTestsPerEvictionRun(1);
> 			INX_POOL2.setSoftMinEvictableIdleTimeMillis(300000);
> 			INX_POOL2.setTimeBetweenEvictionRunsMillis(150000);
> 			INX_POOL2.setMaxTotal(200);
> 			INX_POOL2.setMaxWaitMillis(5000);
> 			INX_POOL2.setTestOnBorrow(false);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message