msm-session-manager and kryo as serialization strategy

96 views
Skip to first unread message

User 123

unread,
Jun 19, 2015, 6:02:51 AM6/19/15
to kryo-...@googlegroups.com
Hi

I would like use msm-session-manager and kryo as serialization strategy.

I use tomcat7, java 8 and following libs:
tomcat/lib:
spymemcached-2.11.1.jar
memcached-session-manager-1.8.3.jar
memcached-session-manager-tc7-1.8.3.jar

WEB-INF/lib:
asm-3.2.jar
kryo-1.04.jar
kryo-serializers-0.11.jar
minlog-1.2.jar
reflectasm-1.01.jar
msm-kryo-serializer-1.8.3.jar

In case of deserialization I get following error and die session will be purged:

WARNUNG: Could not deserialize session with id 97EEBA4851DAE5BE3EBD2CC4D9ED94F8 from memcached, session will be purged from storage.
de.javakaffee.web.msm.TranscoderDeserializationException: com.esotericsoftware.kryo.SerializationException: Unable to deserialize object of type: java.util.concurrent.ConcurrentHashMap
        at de.javakaffee.web.msm.serializer.kryo.KryoTranscoder.deserializeAttributes(KryoTranscoder.java:291)
        at de.javakaffee.web.msm.TranscoderService.deserializeAttributes(TranscoderService.java:171)
        at de.javakaffee.web.msm.TranscoderService.deserialize(TranscoderService.java:128)
        at de.javakaffee.web.msm.MemcachedSessionService.loadFromMemcached(MemcachedSessionService.java:1100)
        at de.javakaffee.web.msm.MemcachedSessionService.findSession(MemcachedSessionService.java:585)
        at de.javakaffee.web.msm.MemcachedBackupSessionManager.findSession(MemcachedBackupSessionManager.java:216)
        at org.apache.catalina.connector.Request.doGetSession(Request.java:2900)
        at org.apache.catalina.connector.Request.getSessionInternal(Request.java:2518)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:427)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
        at de.javakaffee.web.msm.RequestTrackingHostValve.invoke(RequestTrackingHostValve.java:156)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
        at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:603)
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.esotericsoftware.kryo.SerializationException: Unable to deserialize object of type: java.util.concurrent.ConcurrentHashMap
        at com.esotericsoftware.kryo.Kryo.readObject(Kryo.java:593)
        at com.esotericsoftware.kryo.ObjectBuffer.readObject(ObjectBuffer.java:213)
        at de.javakaffee.web.msm.serializer.kryo.KryoTranscoder.deserializeAttributes(KryoTranscoder.java:289)
        ... 20 more
Caused by: com.esotericsoftware.kryo.SerializationException: Unable to deserialize object of type: xxx
        at com.esotericsoftware.kryo.Kryo.readClassAndObject(Kryo.java:571)
        at com.esotericsoftware.kryo.serialize.MapSerializer.readObjectData(MapSerializer.java:129)
        at com.esotericsoftware.kryo.Serializer.readObject(Serializer.java:61)
        at com.esotericsoftware.kryo.Kryo.readObject(Kryo.java:589)
        ... 22 more
Caused by: com.esotericsoftware.kryo.SerializationException: Unable to deserialize object of type: yyy
Serialization trace:
directory (yyy)
        at com.esotericsoftware.kryo.Kryo.readClassAndObject(Kryo.java:571)
        at com.esotericsoftware.kryo.serialize.MapSerializer.readObjectData(MapSerializer.java:129)
        at com.esotericsoftware.kryo.serialize.FieldSerializer.readObjectData(FieldSerializer.java:220)
        at com.esotericsoftware.kryo.serialize.ReferenceFieldSerializer.readObjectData(ReferenceFieldSerializer.java:81)
        at com.esotericsoftware.kryo.Kryo.readClassAndObject(Kryo.java:566)
        ... 25 more
Caused by: com.esotericsoftware.kryo.SerializationException: Unable to deserialize object of type: xxx
Serialization trace:
attributes (yyy)
        at com.esotericsoftware.kryo.Kryo.readClassAndObject(Kryo.java:571)
        at com.esotericsoftware.kryo.serialize.MapSerializer.readObjectData(MapSerializer.java:129)
        at com.esotericsoftware.kryo.serialize.FieldSerializer.readObjectData(FieldSerializer.java:220)
        at com.esotericsoftware.kryo.serialize.ReferenceFieldSerializer.readObjectData(ReferenceFieldSerializer.java:81)
        at com.esotericsoftware.kryo.Kryo.readClassAndObject(Kryo.java:566)
        ... 29 more
Caused by: com.esotericsoftware.kryo.SerializationException: Unable to find class: xxx.lazyloaders.LazyLoadersServiceImpl$$Lambda$94/516742316
Serialization trace:
adAddressBeanLazyLoader (zzz)
lazyLoaders (zzz)
currentInstance (zzz)
        at com.esotericsoftware.kryo.Kryo.readClass(Kryo.java:449)
        at com.esotericsoftware.kryo.serialize.FieldSerializer.readObjectData(FieldSerializer.java:214)
        at com.esotericsoftware.kryo.serialize.ReferenceFieldSerializer.readObjectData(ReferenceFieldSerializer.java:81)
        at com.esotericsoftware.kryo.serialize.FieldSerializer.readObjectData(FieldSerializer.java:220)
        at com.esotericsoftware.kryo.serialize.ReferenceFieldSerializer.readObjectData(ReferenceFieldSerializer.java:81)
        at com.esotericsoftware.kryo.serialize.FieldSerializer.readObjectData(FieldSerializer.java:220)
        at com.esotericsoftware.kryo.serialize.ReferenceFieldSerializer.readObjectData(ReferenceFieldSerializer.java:81)
        at com.esotericsoftware.kryo.Kryo.readClassAndObject(Kryo.java:566)
        ... 33 more
Caused by: java.lang.ClassNotFoundException: xxx.lazyloaders.LazyLoadersServiceImpl$$Lambda$94/516742316
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:340)
        at com.esotericsoftware.kryo.Kryo.readClass(Kryo.java:447)
        ... 40 more


Any ideas whats my problem with this configuration?

Can I use the latest version of kryo V2+ (actually 3.0.2). What are the dependencies and versions I need? How looks the context.xml - I want to use the fast msm-kryo-serializer? It was not possible to me to get this version to run in my configuration.

Hope somebody can help me to solve my problem.

best regards

Martin Grotzke

unread,
Jun 19, 2015, 6:27:16 PM6/19/15
to kryo-users

I'm sorry, but msm does not yet support kryo 3, see also https://code.google.com/p/memcached-session-manager/issues/detail?id=213

Perhaps I find time for it the next weeks for this.

Cheers,
Martin

--
You received this message because you are subscribed to the "kryo-users" group.
http://groups.google.com/group/kryo-users
---
You received this message because you are subscribed to the Google Groups "kryo-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kryo-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Martin Grotzke

unread,
Jul 21, 2015, 6:47:42 PM7/21/15
to kryo-users
Hi,

I just pushed a release candidate of memcached-session-manager with kryo
3 support. I'd be happy if you could test it and give feedback on the
msm mailing list, please check the related announcement there:
https://groups.google.com/d/msg/memcached-session-manager/frIakVdjpV8/LqfrLNqVjTQJ

Cheers,
Martin


On 06/20/2015 12:27 AM, Martin Grotzke wrote:
> I'm sorry, but msm does not yet support kryo 3, see also
> https://code.google.com/p/memcached-session-manager/issues/detail?id=213
>
> Perhaps I find time for it the next weeks for this.
>
> Cheers,
> Martin
>
> Am 19.06.2015 12:02 schrieb "User 123" <12345rai...@gmail.com
> <mailto:12345rai...@gmail.com>>:
> <mailto:kryo-users+...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
>

--
inoio gmbh - http://inoio.de
Schulterblatt 36, 20357 Hamburg
Amtsgericht Hamburg, HRB 123031
Geschäftsführer: Dennis Brakhane, Martin Grotzke, Ole Langbehn

signature.asc
Reply all
Reply to author
Forward
0 new messages