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 35789 invoked from network); 21 Mar 2000 19:15:18 -0000 Received: from ns.lucasfilm.com (HELO brooklyn.lucasfilm.com) (208.244.233.2) by locus.apache.org with SMTP; 21 Mar 2000 19:15:18 -0000 Received: from cerberus.lucasfilm.com ([150.0.40.12]) by brooklyn.lucasfilm.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id F47SK5S5; Tue, 21 Mar 2000 11:14:52 -0800 Received: from malone.lucasdigital.com ([10.10.192.51]) by cerberus.lucasfilm.com; Tue, 21 Mar 2000 11:14:51 +0000 (PST) Received: from lucasdigital.com (ilmpc105 [10.5.9.26]) by malone.lucasdigital.com (8.8.8+Sun/8.8.8/990524-/HUB) with ESMTP id LAA08174 for ; Tue, 21 Mar 2000 11:14:46 -0800 (PST) Message-ID: <38D7CA25.B80976F2@ilm.com> Date: Tue, 21 Mar 2000 11:14:45 -0800 From: Bryan Arntson X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-user@jakarta.apache.org Subject: tomcat 3.1beta caching JSP pages? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I am running tomcat 3.1beta, and an experiencing unusual behavior with JSP's. When I create a JSP, and load it through a browser, I can see the page. If I make half a dozen changes to the JSP page (like change text, or words), and hit reload in the browser, the server correctly determines that the JSP is new, and reloads the changed JSP file. However, after about a dozen or so changes to the page, the behavior of JSP reloading changes. It appears that the server starts to cache the JSP pages, and I start to see previous versions of the JSP page being displayed. It appears that it is not just the previous version of the JSP file, but at least 2 or 3 prevoiously changed JSP files. Is this the correct behavior? Did I not set a parameter correctly for the server? Any help would be greatly appreciated. Thanks, Bryan