Greetings,
         I am facing a servlet caching problem in Tomcat. I create a
servlet .java file compile it and put it in the webapps folder of the
TOMCAT_HOME folder. I start the Tomcat server and invoke the servlet via
http://localhost:<TomCat port no>/servlet/<Servlet name> in Netscpe. It gets
invoked. All is well uptil now.

         Problem comes when I make changes in the .java file, recompile it,
place it in the same TOMCAT_HOME/webapps folder, and again invoke it in
Netscape via http://localhost:<Tomcat Port No>/servlet/<Servlet name>. The
ALTERED sevlet does NOT get invoked, the old servlet is getting invoked.

         This must mean Tomcat is caching its sevlets somewhere, and it is
picking up the servlets from that cache, ignoring the actual .class servlet file in
the webapps folder. Maybe the cache gets cleared everytime Tomcat restarts, but
I find it inconvenient to frequently restart Tomcat.

         So what is the one time solution to this servlet caching problem,
WITHOUT HAVING TO REGULARLY RESTART TOMCAT? Will a startup servlet running
continuosly alongwith Tomcat, performing the servlet cache cleaning
operation- regularly say every 10 seconds- solve the problem? If so then
what should be the coding of the servlet? Should I use classes of the
java.lang.ref package- PhantomReference e.t.c- (
http://java.sun.com/products/jdk/1.2/docs/api/java/lang/ref/package-summary.html
)? Or can some changes in server.xml do the trick?

         I have Apache 1.3.19, Tomcat 3.23 installed, configured and
running on RedHat Linux 6.2 platform.

         Waiting for an early response. Thanks in advance.
                                                             SNODX

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to