ServletRequests are not serializable on purpose - they represent a particular request execution at a particular moment in time. There isn't any reason I can think of to serialize and then deserialize them out of memory.
I suspect something you might be saving in a session attribute has a direct reference to the request. You should make that property transient if so. HTH! Best, -- Les Hazlewood | @lhazlewood CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282 On Wed, Apr 17, 2013 at 4:00 AM, Bernhard Hirschmann <[email protected]> wrote: > I'm having problems with the activeSessionsCache, for which I'm using > WebSphere's DistributedMap. > Seems like the ShiroHttpServletRequest doesn't implement > java.io.Serializable: > > [17.04.13 12:37:18:970 CEST] 00000007 CacheEntry E DYNA0052E: The > cached object can not be replicated or saved to disk. CacheID: > 4f68f164-8d2a-493b-aa98-036f243600a1 ClassName: > org.apache.shiro.session.mgt.SimpleSession Type: cache-value Exception: > java.io.NotSerializableException: > org.apache.shiro.web.servlet.ShiroHttpServletRequest > > I will try to add the Serializable interface, but I'm not sure beeing on the > right path. Any comments about this? > > B. > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/NotSerializableException-for-ShiroHttpServletRequest-tp7578607.html > Sent from the Shiro User mailing list archive at Nabble.com.
