Hello Lidija, could you try out this custom serializer and report back with the results?
https://gist.github.com/duskote/0f8cce8d1b0d1cc56844 On Thu, Mar 6, 2014 at 10:48 AM, Lidija Dolinar <lidija....@gmail.com>wrote: > Ah, I see, you ment SimplePrincipalSerializer from the patch. > > It doesn't effect cookie size much though - it is now 4.3K instead of 4.6K > so it doesn't resolve our problem, cookie is still to big. > > Regards, > Lidija > > > On Thu, Mar 6, 2014 at 10:14 AM, Lidija Dolinar <lidija....@gmail.com > >wrote: > > > By SimplePrincipalSerializer - did you mean this one that uses Kryo? > > > http://grepcode.com/file/repo1.maven.org/maven2/org.jasig.cas/cas-server-integration-memcached/4.0.0-RC1/org/jasig/cas/ticket/registry/support/kryo/serial/SimplePrincipalSerializer.java > > > > Regards, > > Lidija > > > > > > > > On Wed, Mar 5, 2014 at 5:54 PM, Kalle Korhonen < > kalle.o.korho...@gmail.com > > > wrote: > > > >> Ah yes, the size of the default remember me cookie can grow outrageously > >> big because it uses Java serialization. That's long running issue > against > >> Shiro web (https://issues.apache.org/jira/browse/SHIRO-226). It's > simply > >> to > >> override with your own implementation - you could use the one attached > as > >> a > >> patch to the issue, then override the default CookieRememberMeManager > >> with: > >> public class LightCookieRememberMeManager extends > CookieRememberMeManager > >> { > >> public LightCookieRememberMeManager() { > >> super(); > >> setSerializer(new SimplePrincipalSerializer()); > >> } > >> } > >> > >> Kalle > >> > >> >
