Hello and thank you for your email. We strive to respond to all email inquiries within one business day. If your issue cannot wait that long, please call us at 877-438-8966. Our hours are 6:00 a.m. to 6:00 p.m. Pacific Standard Time, Monday through Friday. For reference, your assigned case ID is:986677
-----Original Message----- From: Jon Wingfield [EMAIL PROTECTED] Sent: Friday, Jan 30 2004 2:55AM To: Tomcat Users List [EMAIL PROTECTED] Subject: IOException while loading persisted sessions continued.. Did you read as far as the NotSerializableException bit? ;) If you don't want to make MyLinks serializable but want Tomcat to serialize sessions you could (amongst other things) implement a HttpSessionActivationListener. Add this object to the session at the same time as your MyLinks object. When tomcat serializes the session to disk the sessionWillPassivate() method will be called. In that method you could remove the MyLinks object from the session. When the session is restored you could re-init MyLinks in the sessionDidActivate() implementation. HTH, Jon Allistair Crossley wrote: > It says "Classes that do not implement this interface will not have any of their > state serialized or deserialized" > > So, to me that means I do not have to put Serializable if I do not want my MyLinks > class to be persisted. But Tomcat is throwing an error which means it thinks MyLinks > "should" be Serialized for some reason. > > I do not want MyLinks to be Serializable. Why does Tomcat throw an error for this > object and for no others? > > Thanks ADC > > -----Original Message----- > From: Yiannis Mavroukakis [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] > Sent: 30 January 2004 09:50 > To: 'Tomcat Users List' > Subject: RE: IOException while loading persisted sessions continued.. > > > No this is Java specific, not Tomcat. See > http://java.sun.com/j2se/1.4.2/docs/api/java/io/Serializable.html > <http://java.sun.com/j2se/1.4.2/docs/api/java/io/Serializable.html> > > Yiannis > > -----Original Message----- > From: Allistair Crossley [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] > Sent: 30 January 2004 09:43 > To: TOMCAT USER (E-mail) > Subject: IOException while loading persisted sessions continued.. > > > Yes, but I don't want to may this object Serializable - is this Tomcat > specific? I have plenty of other objects in session but they don't have > these errors thrown?? > Cheers, ADC > -- snip -- > When tomcat persists sessions, it will try to serialize all objects stored > in your sessions to disk. In order to be successful, all the objects must be > serializable. > In this example, the class > com.comp.newmedia.intranet.iq.dto.myiq.mylinks.Link is not serializable - it > does not implement the Serializable interface. > > Vitor > > -- snip -- > > Allistair Crossley wrote: > Hi, > > I quite often but not always get a huge stack trace thrown when Tomcat boots > up the top part of which is the following. I'm not sure why it thinks it > needs to be loading anything to do with my bean here from persisted > sessions. Is that a setting that I have switched on that I need to switch > off? Like I say, only happens on every 3rd or 4th reboot (development > instance) and it does not stop TC5.0.18 working either. > > SEVERE: IOException while loading persisted sessions: > java.io.WriteAbortedExcept > ion: writing aborted; java.io.NotSerializableException: > com.comp.newmedia.intranet.iq.dto.myiq.mylinks.Link > java.io.WriteAbortedException: writing aborted; > java.io.NotSerializableException > : com.comp.newmedia.intranet.iq.dto.myiq.mylinks.Link > at > java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278) > at > java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) > at java.util.LinkedList.readObject(LinkedList.java:702) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ======================================================= This email and its contents are confidential. If you are not the intended recipient, please do not disclose or use the information within this email or its attachments. If you have received this email in error, please delete it immediately. Thank you. ======================================================= --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
