Return-Path: 
 <tomcat-user-return-53389-qmlist-jakarta-archive-tomcat-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 35981 invoked from network); 14 Feb 2003 09:05:58 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 14 Feb 2003 09:05:58 -0000
Received: (qmail 16861 invoked by uid 97); 14 Feb 2003 09:07:39 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org
Received: (qmail 16853 invoked from network); 14 Feb 2003 09:07:38 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 14 Feb 2003 09:07:38 -0000
Received: (qmail 34468 invoked by uid 500); 14 Feb 2003 09:05:33 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 34457 invoked from network); 14 Feb 2003 09:05:33 -0000
Received: from main.gmane.org (80.91.224.249)
  by daedalus.apache.org with SMTP; 14 Feb 2003 09:05:33 -0000
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18jbkl-0003K4-00
	for <tomcat-user@jakarta.apache.org>; Fri, 14 Feb 2003 10:03:27 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: tomcat-user@jakarta.apache.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18jbkk-0003Jd-00
	for <gmane-comp-jakarta-tomcat-user@m.gmane.org>;
 Fri, 14 Feb 2003 10:03:26 +0100
From: =?ISO-8859-1?Q?Sven_K=F6hler?= <skoehler@upb.de>
Subject: Re: AW: modified jsp-files and jasper2
Date: Fri, 14 Feb 2003 10:04:12 +0100
Lines: 65
Message-ID: <b2ibct$cea$1@main.gmane.org>
References: <b2g5e9$9uj$1@main.gmane.org>
 <012401c2d367$40b2d830$fc0110ac@jtrollingerxp> <b2gbdb$1ul$1@main.gmane.org>
 <015a01c2d3cf$76eba180$6400000a@loki>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@main.gmane.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3b) Gecko/20030210
X-Accept-Language: en, de
In-Reply-To: <015a01c2d3cf$76eba180$6400000a@loki>
Sender: news <news@main.gmane.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> It can take up to 15 seconds (default) for Tomcat to poll for changes to
> class files.  The frequency of how often Tomcat checks can be changed via
> the Loader checkInterval property in the containing Context node.  Ensure
> Context.reloadable and Loader.reloadable are not set to false; they are true
> by default.

according to the docs, this config should do:

     <servlet>
         <servlet-name>jsp</servlet-name>
         <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
         <init-param>
             <param-name>logVerbosityLevel</param-name>
             <param-value>WARNING</param-value>
         </init-param>
         <init-param>
             <param-name>compiler</param-name>
             <param-value>jikes</param-value>
         </init-param>
         <init-param>
             <param-name>development</param-name>
             <param-value>false</param-value>
         </init-param>
         <init-param>
             <param-name>reloading</param-name>
             <param-value>true</param-value>
         </init-param>
         <init-param>
             <param-name>checkInterval</param-name>
             <param-value>10</param-value>
         </init-param>
         <load-on-startup>3</load-on-startup>
     </servlet>

BUT:
5 minutes ago, i had a case, where it didn't work.
The page was uploaded an hour ago, but you still couldn't see the 
correct page online. I checked the work-folder, and the jsp-page has 
_not_ been compiled. the old .java and .class file was still there.

Hitting the reload-button in the manager-app always helps.

we also uploaded another update of the same page, and this time, the 
jsp-page was recompiled, and we could see the new page - as it should 
normally be.

The "reloadable" property of the context shouldn't matter, because it's 
for the files in the WEB-INF-folder (it says, whether they can will be 
automatically reloaded or not)

hitting the reload-button in the manager-app shouldn't help at all, 
because the classes generated from JSP-files should be reloaded by Jasper.

Even if i'm wrong, it should always _not_ work, or always work, but not 
like it is now: it works sometimes, but not always

> I am uncertain whether or not JSP files are included in this particular
> check or if there is another layer elsewhere.  But a good guideline is to
> wait for at least 60 seconds before testing newly uploaded JSP files.

You also tell me, that the checkInterval-Option of Jasper is completly 
useless? and i would have to wait 60sec?

We waited more than 60sec, but it didn't work.



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org