I checked in a fix for this last night (though I'm unsure how to
reproduce it). The thread now calls setDaemon(true).
Lloyd
On Apr 11, 2008, at 5:13 AM, Sahoo wrote:
> I see this while running in HK2 mode. The server process stays
> around. I think it is because of this non-daemon thread left by a
> subsystem. I seem to think it is AMX subsystem, because on an older
> build I had seen the thread stack containing AMX methods.
>
> "pool-2-thread-1" prio=10 tid=0x084f0b60 nid=0x27 waiting on
> condition [0xc8b4d000..0xc8b4daa8]
> at sun.misc.Unsafe.park(Native Method)
> at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer
> $ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
> at java.util.concurrent.DelayQueue.take(DelayQueue.java:131)
> at java.util.concurrent.ScheduledThreadPoolExecutor
> $DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:504)
> at java.util.concurrent.ScheduledThreadPoolExecutor
> $DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:497)
> at
> java
> .util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:
> 470)
> at java.util.concurrent.ThreadPoolExecutor
> $Worker.run(ThreadPoolExecutor.java:674)
> at java.lang.Thread.run(Thread.java:595)
>
> I seem to see this while using admingui->registration functionality.
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc