commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: [pool] POOL-97 timer patch
Date Fri, 28 Dec 2007 19:05:14 GMT
Phil Steitz wrote:
> I am not sure whether this is actually a bug, or worth reopening
> POOL-97, but want to be safe rather than sorry before releasing 1.4.
> I am getting JVM hangs with the current code when I fail to close the
> pool.  This did not happen with the 1.3 code.  The (admittedly sloppy)
> code in trunks-sandbox/performance/pool/..PoolSoak, PoolClientThread
> creates a pool that can have an evictor configured (config is in
> pool-config.xml, but neglects to close the pool on termination.  With
> pool 1.3, the JVM terminates normally, but with 1.4 it hangs with
> thread dump that starts like this:
>   [java] Full thread dump Java HotSpot(TM) Client VM (1.5.0_12-b04
> mixed mode, sharing):


I am not sure I am running the right test as I don't see this. Running
org.apache.commons.performance.pool.PoolSoakTest with commons-pool from the
1.4 release branch the test ends normally. I see the same behaviour with
1.6.0_03 and 1.5.0_13 JDKs.

Am I running the right test?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message