Open GoogleCodeExporter opened 8 years ago
OS : Linux x86_64 x86_64 x86_64 GNU/Linux
Original comment by yoga.und...@gmail.com
on 3 Mar 2014 at 11:01
I'd say you're serializing the whole spring ApplicationContext. Or might there
be another reason for such big sessions?
Original comment by martin.grotzke
on 6 Mar 2014 at 12:45
The same application + Coherence Web Session+ Kryo and same application +
Hazelcast Wen Session + Kryo doesn't have this issue. Also we measured the max
size of the session in those two web sessions framework, max session size is 30
KB.
Original comment by yoga.und...@gmail.com
on 6 Mar 2014 at 4:42
msm + Java Serialization + Spring MVC, going good, but I see one or two issue
while serializing SPRING SECURITY CONTEXT. Looking into it now. It seems like
one of our custom authentication class not implemented Serializable, causing
this issue, let me updated once I'm done with testing.
Cannot serialize session attribute SPRING_SECURITY_CONTEXT for session
Thanks
Yoga
Original comment by yoga.und...@gmail.com
on 27 Mar 2014 at 6:32
For this one, can you provide a simple spring app that allows to reproduce the
issue that I could use to debug this?
Original comment by martin.grotzke
on 27 Mar 2014 at 8:12
Hi Martin,
Please find attached Spring Mvc , where I'm still getting lot below exception,
when I remove implements Serializable from User class. This is same happening
in our legacy spring mvc based application. I'm adding Serializable interface
to classes which are failing one by one, but still the list keep on growing.
Mar 28, 2014 5:32:56 PM de.javakaffee.web.msm.JavaSerializationTranscoder
writeAttributes
WARNING: Cannot serialize session attribute
org.springframework.web.context.request.ServletRequestAttributes.DESTRUCTION_CAL
LBACK.scopedTarget.userProfile for session
F26FF1B9DFDFE7C3EB1110F11449A5F3-n2.tomcat1
java.io.NotSerializableException: com.dev.spring.context.JaxWsClientProxy
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
Original comment by yoga.und...@gmail.com
on 31 Mar 2014 at 4:33
Attachments:
Hi Martin,
Any suggestion/direction to avoid the above exception gracefully, because our
legacy application has tons of classes without Serilizable interface
implementation.
Thanks
Yoga
Original comment by yoga.und...@gmail.com
on 31 Mar 2014 at 4:46
Original issue reported on code.google.com by
yoga.und...@gmail.com
on 3 Mar 2014 at 10:55