> From: Christopher Schultz [mailto:[EMAIL PROTECTED] > Subject: Re: NotSerializableException: StandardSessionFacade > > That's the weirdest stack trace I've ever see. readObject calls > something that throws a WriteAbortedException? Totally weird.
We already discussed that, back at the beginning of this thread. It's due to the object being read in not being serializable now. It's not quite clear, however, how the thing got written out in the first place. > I wonder if you have a class that implements its own read/write > methods that calls the wrong method (read calls write or similar). No, it's because the webapp has stored the session object (actually the facade) into the session - for no apparent reason. The facade is not serializable, of course. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
