Return-Path: 
 <users-return-217906-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 96116 invoked from network); 12 Oct 2010 18:16:05 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 12 Oct 2010 18:16:05 -0000
Received: (qmail 93026 invoked by uid 500); 12 Oct 2010 18:16:01 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 92868 invoked by uid 500); 12 Oct 2010 18:16:01 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 92859 invoked by uid 99); 12 Oct 2010 18:16:01 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Oct 2010 18:16:01 +0000
X-ASF-Spam-Status: No, hits=0.7 required=10.0
	tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [76.96.62.40] (HELO qmta04.westchester.pa.mail.comcast.net)
 (76.96.62.40)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Oct 2010 18:15:54 +0000
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88])
	by qmta04.westchester.pa.mail.comcast.net with comcast
	id HpE61f0071uE5Es54uFaMv; Tue, 12 Oct 2010 18:15:34 +0000
Received: from [192.168.1.202] ([69.143.109.145])
	by omta16.westchester.pa.mail.comcast.net with comcast
	id HuFa1f00338FjT13cuFahK; Tue, 12 Oct 2010 18:15:34 +0000
Message-ID: <4CB4A5C4.1070006@christopherschultz.net>
Date: Tue, 12 Oct 2010 14:15:32 -0400
From: Christopher Schultz <chris@christopherschultz.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Disable class monitoring for reloading container classes
References: <BAE7FA6DEC47CE41B484D09EBDDA3AEA0476B1D2@gluon.hq.aldon.com>
 <4CAE3C0B.2060901@christopherschultz.net> <4CAE4113.5000209@pidster.com>
 <4CAF339F.5070806@christopherschultz.net>
 <BAE7FA6DEC47CE41B484D09EBDDA3AEA0476B1E6@gluon.hq.aldon.com>
 <4CAFC571.60908@christopherschultz.net>
 <BAE7FA6DEC47CE41B484D09EBDDA3AEA03845285@gluon.hq.aldon.com>
 <BAE7FA6DEC47CE41B484D09EBDDA3AEA0476B1E7@gluon.hq.aldon.com>
In-Reply-To: <BAE7FA6DEC47CE41B484D09EBDDA3AEA0476B1E7@gluon.hq.aldon.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jane,

On 10/9/2010 11:09 AM, Jane Muse wrote:
> My understanding from the docs is that reloading="false" means you
> can't drop in a war file while tomcat is running and expect it to
> deploy.

No, <Context reloadable="false"> ("reloading" is meaningless) means that
Tomcat will ignore any files within a webapp that have been updated.
<Host autoDeploy="false"> means that Tomcat will not look for .war files
and automatically deploy them.

> reloading="false" means tomcat is not listening / watching if
> something changes in WEB-INF/classes or WEB-INF/web.xml, and reload
> if there's a change.

Correct, if s/reloading/reloadable/.

> If that's what these mean, then we don't need them.

Generally speaking, it's best to set both of these to "false" in
production because you don't want anything to happen automatically.

> We don't have "WatchedResource" set anywhere either. If anyone knows
> of a way to suppress tomcat from watching if something in WEB-INF/lib
> has changed, I think that might work here.

<Context reloadable="false"> ought to do the trick.

> But apparently tomcat is hard wired to reload if it thinks there's a 
> change in that directory.

Only if reloadable="true", which is NOT the default.

> I'm not sure if that would be considered a bug in the O/S, or the
> JVM, or if tomcat can be made to suppress watching this, similar to
> what the autoDeploy and reloading settings provide. Let's put it this
> way, it would be a lot easier to get a change made to tomcat than to
> IBM's O/S, or Oracle's JVM 8-)

Agreed, but it's hard to imagine how this situation would be detectable.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAky0pcQACgkQ9CaO5/Lv0PAmfwCfRHBsjuVKjBB6mGswfiZ4jHMk
TvIAoL/EYf/iIcSsdM0u6eVYs4AwOLfI
=mcCD
-----END PGP SIGNATURE-----

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