is there any trouble???

[GoogleCodeExporter]

msm-kryo-serializer-1.4.0.jar

de.javakaffee.web.msm.serializer.kryo.KryoTranscoder

   /** 
     * {@inheritDoc}
     */
    @Override
    protected MemcachedBackupSession deserialize( final byte[] in ) {
        throw new UnsupportedOperationException( "Session deserialization not implemented." );
    }
the session is deserialized that must have some trouble!

de.javakaffee.web.msm.SessionTrackerValve 
final Object object = _memcached.get( sessionId, _upgradeSupportTranscoder );

Original issue reported on code.google.com by wxy...@gmail.com on 22 Jul 2011 at 10:16

[GoogleCodeExporter]

protected MemcachedBackupSession deserialize( final byte[] in ) is a method for 
session deserialization as it was used by msm 1.2 (kryo wasn't existing at that 
time), afterwards
  public Map<String, Object> deserializeAttributes( final byte[] data )
was introduced and used.

The deserialization for 1.2 was kept for backward compatibility for other 
serializers that existed with msm 1.2.

If you run into a real issue please report this one, "is there any trouble???" 
is not that specific ;-)

Btw, 1.4.0 is not the latest version, I just release 1.5.0. Though, the 
msm-kryo-serializer pom in 1.5.0 as a dependency declaration issue so that 
there'll be 1.5.1 soon, or you can pull updated artifacts from 
https://oss.sonatype.org/content/repositories/releases/de/javakaffee/msm/.

If you have futher questions we can also discuss them on the mailing list. For 
now I close this issue.

Original comment by martin.grotzke on 22 Jul 2011 at 11:20

• Changed state: Invalid