ThreadPoolFilters doesn't stop all worker threads.

• Key: DIRMINA-117
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Trustin Lee
• Reporter: Trustin Lee
• Affects Version/s: 0.8.0
• Fix Version/s: 0.8.1

Description

Paolo Perrucci Wrote:

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).

Comments

Checked in the fix.