tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Hencin" <michael.hen...@edm-concepts.com>
Subject RE: Webapps that run on 5.0.28 but not 5.5.x?
Date Wed, 01 Nov 2006 20:56:14 GMT
Thanks I will pass this along to our programmers. I am in a special position
as we are the webapp supplier and specify as our requirements that the end
clients use Tomcat. 

I therefore look at tomcat in a different light, as a tool. I am always
concerned with what it the most elegant and simplest method to have our web
app work with TC. As our target clients typically do not have TC running at
all, there expertise is novice. I am learning TC more and more and
appreciate the very clear and astute feedback I find here. Thanks.

I am not a programmer and am tasked with writing out installation guide and
handling TC related deployment issues. So this thread in particular is of
concern to me and how I specify our installation guide and requirements. 

When I tested TC 5.5, I also used the recommended 1.4 JRE. And did the two
steps at once. Probably now that would be not the method I should choose for
an upgrade. As I know that our clients already have the 1.4 JDK installed. I
will proceed with just an TC 5.5 upgrade using the previous JAVA install I
used with 5.0.28.

Mike

-----Original Message-----
From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
Sent: Wednesday, November 01, 2006 1:37 PM
To: Tomcat Users List
Subject: RE: Webapps that run on 5.0.28 but not 5.5.x?

> From: Michael Hencin [mailto:michael.hencin@edm-concepts.com] 
> Subject: RE: Webapps that run on 5.0.28 but not 5.5.x?
> 
> This setup is just as we do with 5.0, but when I access our 
> app, I get this error.
> 
> org.apache.jasper.JasperException: setAttribute: 
> Non-serializable attribute

One of the things 5.5 does better than 5.0 is catch errors earlier.  In
this case, it looks like the app is trying to store a non-serializable
attribute into a Session, which expects everything to be serializable.
By default, Tomcat persists sessions across restarts, so serialization
is required.  You can disable this persistence (look in
conf/context.xml); that may not have an effect on this particular
situation, since the problem is being detected during compilation of a
JSP.

 - 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: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message