Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
SEVERE: IOException while loading persisted sessions:
java.io.WriteAbortedException:
writing aborted; java.io.NotSerializableException:
That means this object cannot be persisted on hard disk.
Does it imply that it’s not safe to keep in Session objects that do not implement “Serializable”?
I haven’t heard that there are limitations on saving non-serializable objects in Session object.
It simply means that Tomcat will always keep them in memory, right?
That’s exactly right, yes.
However, many servlet containers will let you get away with it, if they don’t actually need to do any serialization.
For example, Tomcat doesn’t care if the session attributes are serializable or not, unless you enable session replication. It needs to be able to serialize the attributes to replicate them to the other servers in the cluster.
In your case, it seems that the container is trying to persist the session data to disk, which again would require serialization.