[
https://issues.apache.org/jira/browse/POOL-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025813#comment-13025813
]
Phil Steitz commented on POOL-187:
----------------------------------
Look carefully at the clearOldest code. That is almost certainly where the
problem is (since you can see from a thread dump on a stalled execution that
the pool appears exhausted and the test in question is verifying that
clearOldest is creating capacity). The map used to store instances to be
considered for removal has pool keys as *values* not keys (per the comment in
the code). It looks like you reversed that in the parameterization.
> TestGenericKeyedObjectPool.testMaxTotalLRU method falls in an infinite loops
> ----------------------------------------------------------------------------
>
> Key: POOL-187
> URL: https://issues.apache.org/jira/browse/POOL-187
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Simone Tripodi
> Assignee: Simone Tripodi
>
> After having restored the Genrics, the
> TestGenericKeyedObjectPool.testMaxTotalLRU test method is stuck and I didn't
> figure out the reason :(
> That's why I currently put the @Ignore annotation, so JUnit can continue
> running, but I need help to fix it.
> I suspect Continuum is stuck too, but I think I don't have enough karma to
> unlock it.
> Many thanks in advance!!!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira