search

mauriciorodrigues / memcached-session-manager

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

Shutdown kryo when webapp/tomcat is stopping #102

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
When the tomcat running msm with kryo transcoder is stopped, there's a message

SEVERE: The web application [] created a ThreadLocal with key of type 
[com.esotericsoftware.kryo.Kryo$1] (value 
[com.esotericsoftware.kryo.Kryo$1@348dcd5d]) and a value of type 
[com.esotericsoftware.kryo.Context] (value 
[com.esotericsoftware.kryo.Context@49a5af9f]) but failed to remove it when the 
web application was stopped. This is very likely to create a memory leak.

This should be fixed by stopping kryo when the manager (msm) is stopped.

Original issue reported on code.google.com by martin.grotzke on 15 Jul 2011 at 8:15

GoogleCodeExporter commented 8 years ago 
I'm seeing this issue whenever I upload a new jar and reload the webapp.   Any 
update/ETA on a fix?   

Cheers,
Steve

Original comment by steve.lo...@gmail.com on 30 Aug 2013 at 6:07

GoogleCodeExporter commented 8 years ago 
I had a look at this last weekend and it doesn't seem to be fixable that easily.
I'd rather invest time to upgrade to kryo 2 (and what's still needed in 
kryo-serializers for this), then this annoyance is automatically gone.

Original comment by martin.grotzke on 30 Aug 2013 at 8:18

GoogleCodeExporter commented 8 years ago 
that makes sense.  In fact, I actually was curious about kryo 2 support.  
Completely agree that this should be deferred.

Original comment by steve.lo...@gmail.com on 9 Sep 2013 at 1:38