coolbole / memcached-session-manager

Automatically exported from code.google.com/p/memcached-session-manager
0 stars 0 forks source link

tomcat shutdown Failed #197

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
We've got an error  
The web application [/host-manager] appears to have started a thread named 
[Memcached IO over {MemcachedConnection to /172.27.0.242:11211} - SHUTTING DOWN 
(informed client)] but has failed to stop it. This is very likely to create a 
memory leak.

when shutdown Tomcat7

What steps will reproduce the problem?
1. configure msm
2. start tomcat
3. shutdown tomcat

What is the expected output? What do you see instead?
good shutdown

What version of the product are you using? On what operating system?
msm-1.8.1  +tc7-1.8.1
tomcat 7

our msm configuration
<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
    memcachedNodes="<CACHE_ENDPOINT>"
    sticky="false"
    lockingMode="auto"
    requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js)$"
    sessionBackupAsync="false"
    sessionBackupTimeout="100"
    />

thanks to solve this error

Original issue reported on code.google.com by gaetan.r...@gmail.com on 25 Feb 2014 at 3:52

GoogleCodeExporter commented 9 years ago
msm obviously has asked the MemcachedClient to shutdown (see the thread name 
"SHUTTING DOWN (informed client)" and check the sources here: 
https://github.com/couchbase/spymemcached/blob/master/src/main/java/net/spy/memc
ached/MemcachedClient.java#L2373).

Additionally I'd say tomcat logs a warning and you don't have a real 
application issue (of course it would be nice not to get this warning).

What do you think is the issue in msm?

Original comment by martin.grotzke on 27 Feb 2014 at 11:57