[ https://issues.apache.org/jira/browse/POOL-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651820#comment-17651820 ]
Niall Pemberton commented on POOL-264: -------------------------------------- The synchronization was removed in May 2011 when it was refactored to use java.util.concurrent based pooling: * [https://svn.apache.org/viewvc?view=revision&revision=1102500] This change was included in the Pool 2.0 release (Java 1.5 minimum) but not in any of the Pool 1.x versions (Java 1.3 minimum). > NullPointerException in GKOP.borrowObject() > ------------------------------------------- > > Key: POOL-264 > URL: https://issues.apache.org/jira/browse/POOL-264 > Project: Commons Pool > Issue Type: Bug > Affects Versions: 1.5.6, 1.5.7, 1.6 > Reporter: Leonid Meyerguz > Priority: Major > > While I cannot pin down a consistent repro, I occasionally observe a > NullPointerException at > org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1126) > The pool is configured as follows: > maxActive = -1 > maxIdle = 32 > maxTotal = 32 > whenExhaustedAction = WHEN_EXHAUSTED_GROW > timeBetweenEvictionRunsMillis = 20000 > minEvictableIdleTimeMillis = 60000 > numTestsPerEvictionRun = -1 > The NullPointerException is thrown in the WHEN_EXHAUSTED_GROW branch of the > code. Specifically it appears that latch.getPool() returns null. > Any suggestions for a work-around would be appreciated. -- This message was sent by Atlassian Jira (v8.20.10#820010)