Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 37478 invoked from network); 6 Sep 2003 20:50:06 -0000 Received: from unknown (HELO www.meritonlinesystems.com) (68.157.175.145) by daedalus.apache.org with SMTP; 6 Sep 2003 20:50:06 -0000 Received: from [192.168.1.10] (alice.meritonlinesystems.com [192.168.1.10]) by www.meritonlinesystems.com (8.11.6/8.11.6) with ESMTP id h86Knvn16835 for ; Sat, 6 Sep 2003 16:49:57 -0400 Subject: class files being cached? From: Mike Millson Reply-To: mmillson@meritonlinesystems.com To: Tomcat Users List Content-Type: text/plain Organization: Merit Online Systems, Inc. Message-Id: <1062881397.2361.22.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 06 Sep 2003 16:49:58 -0400 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I have a tomcat 3.3.1 application that I suspect might be caching old class files. The application consists of about 50 servlet classes (I'm using straight servlets, not JSPs) deployed as a jar file. When I update the jar file, I think some of the old classes are not being replaced w/ the new ones. Will any of the following cause servlet classes to be cached between stop/starts: 1) Not clearing the /work directory. Can this directory have anything to do with servlets being cached? Or does tomcat strictly use it to compile JSPs? 2) Storing old jar files in the WEB-INF/lib with extensions other than .jar. For example, can I rename app.jar to app.jar.20030906 and leave it in WEB-INF/lib along with the new app.jar file, or could this cause servlet caching issues? Mike