[
https://issues.apache.org/jira/browse/POOL-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-376:
-----------------------------
Affects Version/s: 2.6.1
2.7.0
> invalidateObject should not return NullPointerException
> -------------------------------------------------------
>
> Key: POOL-376
> URL: https://issues.apache.org/jira/browse/POOL-376
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 2.6.1, 2.6.2, 2.7.0
> Reporter: M Sazzadul Hoque
> Priority: Critical
> Labels: pull-request-available, pull-requests-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{GenericObjectPool.invalidateObject(T obj)}} should not return
> {{NullPointerException}} when obj is not null.
> Please see following stack trace:
> {code:java}
> Caused by: java.lang.NullPointerException
> at
> org.apache.commons.pool2.impl.LinkedBlockingDeque.putLast(LinkedBlockingDeque.java:454)
> at
> org.apache.commons.pool2.impl.LinkedBlockingDeque.put(LinkedBlockingDeque.java:788)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.destroy(GenericObjectPool.java:939)
> at
> org.apache.commons.pool2.impl.GenericObjectPool.invalidateObject(GenericObjectPool.java:618)
> {code}
> Apparent reason: In {{destroy(PooledObject<T> toDestroy)}}, create() may
> return null even though {{toDestroy}} is already destroyed.
> *Please make the fix available for JDK 1.7.*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
