[
https://issues.apache.org/jira/browse/POOL-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104781#comment-14104781
]
Phil Steitz commented on POOL-270:
----------------------------------
The code looks correct to me and there are unit tests that confirm correct
setting of config values by constructors. I don't see anywhere that
minEvictableIdleTimeMillis is used to control a timer or override
timeBetweenEvictionRunsMillis. Perhaps your client code is swapping these or
you are not correctly understanding the meaning of these config parameters.
> timeBetweenEvictionRunsMillis from config is ignored
> ----------------------------------------------------
>
> Key: POOL-270
> URL: https://issues.apache.org/jira/browse/POOL-270
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Michael Berman
>
> In the constructors for both GenericObjectPool and GenericKeyedObjectPool,
> the setting for timeBetweenEvictionRunsMillis is always overridden by
> minEvictableIdleTimeMillis.
> First setConfig() is called, which, ends up starting an evictor with a period
> of timeBetweenEvictionRunsMillis, as expected. but the final line of the
> constructor calls startEvictor() again with minEvictableIdleTimeMillis, which
> kills the first timer and starts a new one with the new period. This means
> effectively the timeBetweenEvictionRunsMillis from the config is not used for
> anything.
> I want testWhileIdle's verifications to run more often than I want the
> timeout for evicting idle objects, which does not appear to be possible given
> this bug.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
