tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julius Davies" <>
Subject RE: Tomcat 4.1 Caching Classes?
Date Thu, 24 Oct 2002 00:55:41 GMT

Hello, Kendall Gifford,

That's really weird behaviour you're reporting.  I've never studied any portion of Tomcat's
code, so I cannot make any definitive statements regarding Tomcat, especially anything undocumented.

However, I have had the same thing happen to me.  It turned out to be completely my own fault:
 in a switch from one platform to another (and the many, many changes that can entail) the
order in which different versions of the same class were loaded somehow changed on me.

The thing about including different versions (the different versions being:  NEW GOOD ONE
and OLD BAD ONE) of the same class in the classpath is that there seems to be a relatively
good (~75-80%???) chance that on your original platform you'll load the NEW GOOD ONE.  However,
there seems to be a 100% chance that when you switch to a different platform, you'll load
the OLD BAD ONE instead.

And you'll go insane.  

This could be what's happening to you...    


Julius Davies, Programmer, CUCBC
Email:, Ph: 604.730.6385

> -----Original Message-----
> From: Kendall Gifford []
> Sent: Wednesday, October 23, 2002 2:02 PM
> To:
> Subject: Tomcat 4.1 Caching Classes?
> Hello all, I've a question regarding some strange (undocumented?) 
> caching behavior in Tomcat. We've been moving some code (mostly JSP's 
> with some supporting classes) from a server running an older (3.x?) 
> version of Tomcat to a FreeBSD 4.7-STABLE server running Tomcat 4.1.
> Since this transition, there have been a few problems and some 
> classes, used by all the JSP's in an entire context, needed to be
> modified. This exposed some odd behavior, the topic of this post. We 
> noticed that after we replaced the class file and restarted Tomcat,
> the web application behaved as though it still had the old version of
> the class file.
> To test if there was some caching going on, the class file was
> completely removed and Tomcat restarted. The web application STILL
> behaved as if the class file were still there. Note that this is an
> independent class file and not a JSP page we're talking about. But,
> just to be safe, when restarting Tomcat we also cleaned out the
> context's work directory as well.
> Does anyone have any idea what might be causing this behavior? Is
> there some place where Tomcat is caching class files (not in the work
> directory)?
> Any help is appreciated. Thanks!
> -- 
> ----------------------------------------
> NO HTML/RTF EMAILS!        /  \
>                             \  /
> Kendall P. Gifford          \/
>           /\
>   /  \
> ----------------------------------------
> --
> To unsubscribe, e-mail:   
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message