[ https://issues.apache.org/jira/browse/POOL-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694311#comment-16694311 ]
ASF GitHub Bot commented on POOL-359: ------------------------------------- Github user grimreaper commented on the issue: https://github.com/apache/commons-pool/pull/17 hrm... or at least its not consistent. I just ran it twice more and failed only once. ∴mvn test -Dtest=TestGenericObjectPool#testCloseMultiplePools I'm not generally the biggest fan of tests that don't rely on a fixed clock: you're guaranteed to eventually get a failure. > NullPointerException closing multiple GenericObjectPools > -------------------------------------------------------- > > Key: POOL-359 > URL: https://issues.apache.org/jira/browse/POOL-359 > Project: Commons Pool > Issue Type: Bug > Affects Versions: 2.6.0 > Reporter: Michael Wintermeyer > Priority: Major > > {code:java} > java.lang.NullPointerException > at org.apache.commons.pool2.impl.EvictionTimer.cancel(EvictionTimer.java:97) > at > org.apache.commons.pool2.impl.BaseGenericObjectPool.startEvictor(BaseGenericObjectPool.java:753) > at > org.apache.commons.pool2.impl.GenericObjectPool.close(GenericObjectPool.java:694) > {code} > Possible when multiple pools in the same process each call #close. > GenericObjectPool#close checks #isClosed before proceeding, but that call > checks a non-static instance variable. It calls into EvictionTimer#cancel > which sets the _static_ variable EvictionCache.executor to null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)