Hi, Glad you've solved it. An extra tip on this issue: the commons-lang (http://jakarta.apache.org/commons/lang/) SerializationUtils class is useful in quickly testing whether a complex object graph can be serialized or not. I use it every now and then and it's been great. Hopefully you or others might find it useful in the future.
Yoav Shapira http://www.yoavshapira.com >-----Original Message----- >From: Steve Kirk [mailto:[EMAIL PROTECTED] >Sent: Friday, December 10, 2004 2:19 PM >To: 'Tomcat Users List' >Subject: RE: sessionS info persistence when restart Tomcat > > >You are of course right ;) I was just experiencing temporary blindness. > >I had overlooked an underlying grandparent class of my User class which was >in the Session; the grandparent contains a reference to its creator, which >is the culprit mentioned in the Exception. This in itself is a nasty that >I >wasn't aware of, so that's 2 things to fix now. > >All solved now :) thanks Yoav/Ben. > >> -----Original Message----- >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >> Sent: Friday 10 December 2004 14:03 >> To: Tomcat Users List >> Subject: RE: sessionS info persistence when restart Tomcat >> >> >> >> Hi, >> Tomcat is not throwing that exception just because it feels >> like it. An >> instance of that class must be reachable in the serialization >> process of >> at least of the session attributes. >> >> Yoav Shapira http://www.yoavshapira.com >> >> >> >-----Original Message----- >> >From: Steve Kirk [mailto:[EMAIL PROTECTED] >> >Sent: Friday, December 10, 2004 8:25 AM >> >To: 'Tomcat Users List' >> >Subject: RE: sessionS info persistence when restart Tomcat >> > >> > >> >no. I've checked this by adding more debug code to my SessionLogger >> class >> >(which implements all the Listener interfaces). Every time a session >> event >> >is fired, my listener code lists all the session attribute names and >> values >> >to the log. So when I shutdown TC, the log output looks like this: >> > >> >2004-12-10 12:08:25 StandardContext[/ao]*** SESSION EVENT: >> >sessionWillPassivate, >> >[EMAIL PROTECTED] >> >2004-12-10 12:08:25 StandardContext[/ao]logSessionAttributes() called >> >2004-12-10 12:08:25 StandardContext[/ao]session >> attribute:TEST1=TestString >> >2004-12-10 12:08:25 StandardContext[/ao]session >> >attribute:[EMAIL PROTECTED] >> >2004-12-10 12:08:25 StandardContext[/ao]session >> >attribute:LOGGED_IN_USER=[ID=1,TS='2004-09-15 >> >18:14:33.0',GUIDELINEFILENAME='user1.html',COMPANYID='0',FIRS >> TNAME='sup >> er', >> >L >> >ASTNAME='user',TITLE='superuser',KNOWNAS='superuser',EMAILADD >> RESS='ao.s >> uper >> >u >> >[EMAIL PROTECTED]',PHONE='01234 superuser',MOBILE='07777 >> >super',USERNAME='su',PASSWORD='super',ACTIVE='Y',BRANDID='1'] >> >2004-12-10 12:08:25 StandardContext[/ao]num attributes:3 >> > >> >So the object named in the log message is not in the >> session. What is >> in >> >the session is core.sql.bean.User, which is a class of my own design >> that >> >basically just has a load of data fields in it (String, Timestamp, >> int). >> >The blurb you can see in the log is the output of the toString() >> method, >> >which just concats the fields together. It's parent and >> subclasses are >> all >> >Serializable. So is the SessionLogger itself. >> > >> >> -----Original Message----- >> >> From: Ben Souther [mailto:[EMAIL PROTECTED] >> >> Sent: Friday 10 December 2004 13:14 >> >> To: Tomcat Users List >> >> Subject: RE: sessionS info persistence when restart Tomcat >> >> >> >> >> >> > INFO: Cannot serialize session attribute LOGGED_IN_USER >> >> > > for session 58FD0ECF29BDCEB9DC096C5DF57A1DCC >> >> > > java.io.NotSerializableException: >> >> > > core.servlet.processor.SubmitLogin >> >> > > at >> >> >> >> > is certainly *not* the class of any object stored in the >> >> > session - I have >> >> >> >> Do you have a reference to it in any of the objects stored in your >> >> session? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: >> [EMAIL PROTECTED] >> >> >> >> >> > >> > >> > >> >--------------------------------------------------------------------- >> >To unsubscribe, e-mail: [EMAIL PROTECTED] >> >For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> This e-mail, including any attachments, is a confidential >> business communication, and may contain information that is >> confidential, proprietary and/or privileged. This e-mail is >> intended only for the individual(s) to whom it is addressed, >> and may not be saved, copied, printed, disclosed or used by >> anyone else. If you are not the(an) intended recipient, >> please immediately delete this e-mail from your computer >> system and notify the sender. Thank you. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
