tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remy Maucherat" <>
Subject Re: TC 4.0.1: classes being cached - requires restart to update
Date Fri, 09 Nov 2001 20:34:12 GMT
> I am using Tomcat in it's standalone mode.
> I am doing work on a class that is being imported by a jsp. I have not
found no
> reliable way to not have tomcat hold the contents of the class in memory.
I am
> forced to restart to get tomcat to show the changes which is a big drag on
> debug cycle.
> I have the following server.xml config flags for the context:
> debug="0"
> reloadable="true"
> cachingAllowed="false"

Remove the cachingAllowed attribute, it won't help (it will only reduce

> despite this, changes made to an imported class never show up unless I
stop and
> start tomcat standalone. I have tried deleteing the class file for the
> class file -- interestingly, it gets recompiled but the new version is not
> one i see in use unless i restart. I have also tried trashing both the jsp
> servlet class file and the class file and various combinations, nothing
> regarding the imported class seems to be effected by messing with the
> is there a config I am missing? a bug? short of this, is there a
> workaround than restarting tomcat?

It works for me (tried with the JSP dates example; modifying the helper bean
class causes the reloading).

The bean class must be in /WEB-INF/classes.


To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message