During some tests of my server I found a strange shutdown problem.
After calling the unbindAll() method my application doesn't exit.
Analyzing the thread dump (requested 2 minutes after shutdown) of the
vitual machine I found this thread:

"ProtocolThreadPool-12" prio=1 tid=0x082985c8 nid=0x4452 in
Object.wait() [5b60b000..5b60b854]
at java.lang.Object.wait(Native Method)
- waiting on <0x477d7460> (a org.apache.mina.util.BlockingQueue)
at java.lang.Object.wait(Object.java:429)
at
org.apache.mina.util.BlockingQueue.waitForNewItem(BlockingQueue.java:55)
- locked <0x477d7460> (a org.apache.mina.util.BlockingQueue)
at
org.apache.mina.util.BaseThreadPool$Worker.fetchBuffer(BaseThreadPool.java:3
76)
- locked <0x477d7460> (a org.apache.mina.util.BlockingQueue)
at
org.apache.mina.util.BaseThreadPool$Worker.run(BaseThreadPool.java:350)

It's the only non daemon blocked thread alive, so the vm doesn't exit.
I think this may be a bug.

I'm using the 0.8.1 snapshot (checked out this morning at 11:00 CET).

Paolo

[ Post a follow-up to this message ]

I'll investigate on it soon.

BTW could you please add '[mina]' prefix to your message subject?

Cheers,
Trustin

2005/11/5, Paolo Perrucci <p.perrucci-rA2pRtUFECGonA0d6jMUrA@public.gmane.org>:
>
> During some tests of my server I found a strange shutdown problem.
> After calling the unbindAll() method my application doesn't exit.
> Analyzing the thread dump (requested 2 minutes after shutdown) of the
> vitual machine I found this thread:
>
> "ProtocolThreadPool-12" prio=1 tid=0x082985c8 nid=0x4452 in
> Object.wait() [5b60b000..5b60b854]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x477d7460> (a org.apache.mina.util.BlockingQueue)
> at java.lang.Object.wait(Object.java:429)
> at
> org.apache.mina.util.BlockingQueue.waitForNewItem(BlockingQueue.java:55)
> - locked <0x477d7460> (a org.apache.mina.util.BlockingQueue)
> at
> org.apache.mina.util.BaseThreadPool$Worker.fetchBuffer(BaseThreadPool.java
> :376)
> - locked <0x477d7460> (a org.apache.mina.util.BlockingQueue)
> at
> org.apache.mina.util.BaseThreadPool$Worker.run(BaseThreadPool.java:350)
>
> It's the only non daemon blocked thread alive, so the vm doesn't exit.
> I think this may be a bug.
>
> I'm using the 0.8.1 snapshot (checked out this morning at 11:00 CET).
>
> Paolo
>
>
>


--
what we call human nature is actually human habit
--
http://gleamynode.net/

[ Post a follow-up to this message ]

I checked in the fix after some regression test. Please let me know if this
problem occurs again. Now I'm deploying the JAR...

Thanks,
Trustin

2005/11/5, Paolo Perrucci <p.perrucci-rA2pRtUFECGonA0d6jMUrA@public.gmane.org>:
>
> During some tests of my server I found a strange shutdown problem.
> After calling the unbindAll() method my application doesn't exit.
> Analyzing the thread dump (requested 2 minutes after shutdown) of the
> vitual machine I found this thread:
>
> "ProtocolThreadPool-12" prio=1 tid=0x082985c8 nid=0x4452 in
> Object.wait() [5b60b000..5b60b854]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x477d7460> (a org.apache.mina.util.BlockingQueue)
> at java.lang.Object.wait(Object.java:429)
> at
> org.apache.mina.util.BlockingQueue.waitForNewItem(BlockingQueue.java:55)
> - locked <0x477d7460> (a org.apache.mina.util.BlockingQueue)
> at
> org.apache.mina.util.BaseThreadPool$Worker.fetchBuffer(BaseThreadPool.java
> :376)
> - locked <0x477d7460> (a org.apache.mina.util.BlockingQueue)
> at
> org.apache.mina.util.BaseThreadPool$Worker.run(BaseThreadPool.java:350)
>
> It's the only non daemon blocked thread alive, so the vm doesn't exit.
> I think this may be a bug.
>
> I'm using the 0.8.1 snapshot (checked out this morning at 11:00 CET).
>
> Paolo
>
>
>


--
what we call human nature is actually human habit
--
http://gleamynode.net/

[ Post a follow-up to this message ]