Martin Grotzke
Martin Grotzke
Thanks for reporting! Do you want to submit a fix for this?
@Wavesonics Great to see interest - do you want to submit a pull request? :-)
Thanks for the PR! Re 1) Yes it might break clients. Because removing serializers is an incompatible change we'd have to bump the major version anyways, this is the chance...
Do you want to submit a PR?
I'd suggest to check out how hibernate proxy implements Java serialization and then implement it for kryo. Alternatively you could have a look at hibernate proxy serialization of other serialization...
Could you exclude the dependency on kryo when depending on kryo-serializers? And depend on kryo-shaded explicitly?
Sure. Let me see when I find the time for this.
Setting session timeout in web.xml should work. The session is stored in memcached with a related expiration. Because there are optimizations that attempt to reduce the number of session updates...
Can you reproduce your issue with the samples provided in https://github.com/magro/memcached-session-manager/tree/master/samples?
Sorry for the long delay! Several people reported issues with AWS. Can you get it running locally? This would show that the issues are not related to the app but...