[ https://issues.apache.org/jira/browse/POOL-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz resolved POOL-270. ------------------------------ Resolution: Fixed Fix Version/s: 2.3 Fixed in r1621664. > 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 > Fix For: 2.3 > > > In the constructor for 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.3.4#6332)