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):
[java] "DestroyJavaVM" prio=1 tid=0x08ead7e8 nid=0x2f7b waiting
on condition [0x00000000..0xbfd728c0]
[java] "Timer-0" prio=1 tid=0x08ea50c8 nid=0x2f88 in
Object.wait() [0xb1139000..0xb1139f30]
[java] at java.lang.Object.wait(Native Method)
[java] - waiting on <0x88eb8300> (a java.util.TaskQueue)
[java] at java.util.TimerThread.mainLoop(Timer.java:509)
[java] - locked <0x88eb8300> (a java.util.TaskQueue)
[java] at java.util.TimerThread.run(Timer.java:462)
Would appreciate any comments on this and suggestions for what, if
any, warning should go into the release notes. What is in changes.xml
now is what the notes are generated from.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
