X Memcached Reactor threads still running when Tomcat hot deploys WAR application

What steps will reproduce the problem?
1. Make a code change on a deployed application
2. Tomcat 6.0.36 tries to re-deploy the application
3. Get error messages on the console. (log attached)

What is the expected output? What do you see instead?
No error messages. Instead,i get these - 

Oct 25, 2013 9:04:10 PM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/hello] appears to have started a thread named 
[Xmemcached-Reactor-0] but has failed to stop it. This is very likely to create 
a memory leak.
Oct 25, 2013 9:04:10 PM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/hello] appears to have started a thread named 
[Xmemcached-Reactor-1] but has failed to stop it. This is very likely to create 
a memory leak.

What version of the product are you using? On what operating system?
using xmemcached-1.4.2 on Windows 7 Enterprise 64 bit

Please provide any additional information below.

Also, when the redeploy proceeds after the error messages posted above, get 
these error messages - 

Exception in thread "Xmemcached-Reactor-0" java.lang.NullPointerException
    at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:383)
    at ch.qos.logback.classic.Logger.error(Logger.java:558)
    at com.google.code.yanf4j.nio.impl.Reactor.dispatchEvent(Reactor.java:325)
    at com.google.code.yanf4j.nio.impl.Reactor.run(Reactor.java:142)
Exception in thread "Heal-Session-Thread" java.lang.NullPointerException
    at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:383)
    at ch.qos.logback.classic.Logger.error(Logger.java:558)
    at net.rubyeye.xmemcached.impl.MemcachedConnector$SessionMonitor.run(MemcachedConnector.java:154)

Original issue reported on code.google.com by rohit.ja...@gmail.com on 26 Oct 2013 at 4:16

Attachments:

memcached_errorlog.png

yunhuizhu / memcached

X Memcached Reactor threads still running when Tomcat hot deploys WAR application #346