[
https://issues.apache.org/jira/browse/POOL-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047165#comment-14047165
]
Phil Steitz commented on POOL-265:
----------------------------------
>From the information provided it is not clear whether this is a user question
>or an actual bug report. Please ask usage questions on the user list.
If you think you have identified a bug, please try to construct a unit test or
a more detailed report showing exactly what is going on. There is an existing
unit test that verifies correct behavior of soft eviction called
testEvictionSoftMinIdle in TestGenericObjectPool. If it is missing something,
you may be able to modify it or use the infrastructure it uses to generate a
failure.
> 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.2#6252)
