[ http://issues.apache.org/jira/browse/POOL-89?page=all ]
Sandy McArthur resolved POOL-89.
--------------------------------
Resolution: Fixed
I've bumped the Thread.sleeps from 10 ms to 25 ms. Reopen this issue if that
isn't enough to stop the false negatives.
> Inconsistency with TestGenericKeyedObjectPool.testMaxTotalLRU
> -------------------------------------------------------------
>
> Key: POOL-89
> URL: http://issues.apache.org/jira/browse/POOL-89
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: Nightly Builds
> Environment: Windows XP, Sun JDK 1.4.2_09
> Reporter: Holger Hoffstätte
> Assigned To: Sandy McArthur
> Priority: Minor
>
> While working on POOL-88 I noticed that *sometimes* testMaxTotalLRU fails:
> junit.framework.AssertionFailedError: expected same:<a0> was not:<a5>
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.failNotSame(Assert.java:278)
> at junit.framework.Assert.assertSame(Assert.java:242)
> at junit.framework.Assert.assertSame(Assert.java:249)
> at
> org.apache.commons.pool.impl.TestGenericKeyedObjectPool.testMaxTotalLRU(TestGenericKeyedObjectPool.java:278)
> This seems to be a timing issue - Thread.sleep(10) is (in my experience) way
> too small as interval to be reliable. I first suspected some obscure breakage
> with my patch but could still reproduce this when simply running
> testMaxTotalLRU repeatedly against the virgin version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
