Only put objects into the session that are serializable. This is a best practice anyway. Tomcat complains about CoyoteRequestFacade not being serializable because it isn't. If you need data from the request (parameter, attributes etc.) in your session then extract them and put them alone into the session.

Or you could simply ignore the error messages at startup.


[EMAIL PROTECTED] wrote:
Can any one help me out in this issue?

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Thursday, August 04, 2005 11:27 AM
To: tomcat-user@jakarta.apache.org
Subject: RE: How to turn off perssitent sessions in Tomcat 4.1?


I am waiting for a good response.
Can any body help me out in this?


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Wednesday, August 03, 2005 6:01 PM
To: tomcat-user@jakarta.apache.org
Subject: RE: How to turn off perssitent sessions in Tomcat 4.1?


Hi Edgar,

Thanks for the reply.
But I am using Tomcat 4.1.29 and I tried this option (I mean,
pathname="" in Manager element of server.xml) in Tomcat 4.1.29, which is
not successful. Is there any way to turn off session persistence in
Tomcat 4.1 itself or I need to upgrade to Tomcat 5.0.

In order to avoid the exception we have to make all the objects that is
put in session to be serializable, right no?.

I am using struts framework. So by default all form beans are
serializable and all primitive data types are also serializable.


Why Tomcat complains about CoyoteRequestFacade is not serializable?


Please clarify my doubts.
Advance thanks to all of u !!!

-----Original Message-----
From: Edgar Alves [mailto:[EMAIL PROTECTED]

Sent: Wednesday, August 03, 2005 5:00 PM
To: Tomcat Users List
Subject: Re: How to turn off perssitent sessions in Tomcat 4.1?

Hi,
  On Tomcat 5.5 you can turn persistent session loading off by setting
the SessionManager pathname attribute to "". Hope that helps.

  -- Edgar Alves

[EMAIL PROTECTED] wrote:


Hi,




I am using Apache+Tomcat 4.1.29 for running my application. When I am
restarting Tomcat I am getting persistent session loading exception

like

this:




2004-03-11 13:52:18 StandardManager[] IOException while loading
persisted sessions:


 java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:


 org.apache.coyote.tomcat4.CoyoteRequestFacade

 java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:


 org.apache.coyote.tomcat4.CoyoteRequestFacade

         at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)

         at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845

)

         at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)

         at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:164

6

)

         at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)

         at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845

)

         at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)

         at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:164

6

)

         at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)

         at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)

         at




org.apache.catalina.session.StandardSession.readObject(StandardSession.

j

ava:1369)




I am not using clustering. I want to turn off the session persistence

in

Tomcat 4.1.29?

I have tried so many options with StandardManager in server.xml. But I
was not successful.

Please help me out in this?




Regards

AK








---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Confidentiality Notice


The information contained in this electronic message and any attachments
to this message are intended
for the exclusive use of the addressee(s) and may contain confidential
or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or
[EMAIL PROTECTED] immediately
and destroy all copies of this message and any attachments.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Confidentiality Notice


The information contained in this electronic message and any attachments
to this message are intended
for the exclusive use of the addressee(s) and may contain confidential
or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or
[EMAIL PROTECTED] immediately
and destroy all copies of this message and any attachments.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Confidentiality Notice


The information contained in this electronic message and any attachments to 
this message are intended
for the exclusive use of the addressee(s) and may contain confidential or 
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL 
PROTECTED] immediately
and destroy all copies of this message and any attachments.

---------------------------------------------------------------------
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]

Reply via email to