Hello Les, thanks for your help -- thats seems to be a good thought.
Seems like the class ShiroHttpSession has a field currentRequest of the type HttpServletRequest. If the session is beeing serialized for the sync between the cluster members, then this might cause the problem. But if this really is the problematic spot, why don't other developers have this problem? Still confusing for me.. -- View this message in context: http://shiro-user.582556.n2.nabble.com/NotSerializableException-for-ShiroHttpServletRequest-tp7578607p7578617.html Sent from the Shiro User mailing list archive at Nabble.com.
