HashedWheelTimer.stop() fails

[002244]

Greetings! 

I have encountered a problem running Netty's Timer facility:

1. Created one single Timer instance for a whole application on start.
"Timer timer = new HashedWheelTimer(50, TimeUnit.MILLISECONDS, 64)"
2. Created three instances of TimerTask
3. Scheduled these tasks multiple times with newTimeout(...) using different
producers.
4. Called stop() on application shutdown

It finished like this:

"Hashed wheel timer #1" prio=3 tid=0x003f9400 nid=0x17 waiting on condition
[0xfa801000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
        at java.lang.Thread.sleep(Native Method)
        at
org.jboss.netty.util.HashedWheelTimer$Worker.waitForNextTick(HashedWheelTimer.java:426)
        at
org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:357)
        at
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
        at java.lang.Thread.run(Thread.java:619)


And the Apache Tomcat reported that:

Jun 23, 2010 3:58:53 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Hashed
wheel timer #1] but has failed to stop it. 
This is very likely to create a memory leak.

Is there's something conceptually wrong I miss?


Thank You for a wonderful framework Netty^^.

-- 
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/HashedWheelTimer-stop-fails-tp5213062p5213062.html
Sent from the Netty User Group mailing list archive at Nabble.com.