Return-Path: 
 <users-return-217716-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 35544 invoked from network); 7 Oct 2010 10:27:02 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 7 Oct 2010 10:27:02 -0000
Received: (qmail 78997 invoked by uid 500); 7 Oct 2010 10:26:58 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 78821 invoked by uid 500); 7 Oct 2010 10:26:55 -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 78812 invoked by uid 99); 7 Oct 2010 10:26:54 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Oct 2010 10:26:54 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Oct 2010 10:26:46 +0000
Received: from [192.168.245.129] (p549E85F6.dip0.t-ipconnect.de
 [84.158.133.246])
	by tor.combios.es (Postfix) with ESMTPA id 4B98B226444
	for <users@tomcat.apache.org>; Thu,  7 Oct 2010 12:23:00 +0200 (CEST)
Message-ID: <4CADA039.7090409@ice-sa.com>
Date: Thu, 07 Oct 2010 12:26:01 +0200
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: Tomcat Users List <users@tomcat.apache.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
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>
 <4CACDD1B.4000103@ice-sa.com>
 <BAE7FA6DEC47CE41B484D09EBDDA3AEA0476B1D6@gluon.hq.aldon.com>
In-Reply-To: <BAE7FA6DEC47CE41B484D09EBDDA3AEA0476B1D6@gluon.hq.aldon.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Jane Muse wrote:
> Andr� - you are correct. We actually modified "autoDeploy" attribute on the <Host> element to false,
  and not "reloadable" in the application context xml, and then it worked on IBM I V7R1.
  Your 3rd point below is probably the key to why it works on one version of the O/S and 
not the other.
  The version where it does not work is Java 1.5.0, and where it does is Java 1.6.0.
  I have a question into IBM to see if I can change the Java used by the O/S.

I believe that if you phrased the question like that, they may not understand what you 
mean, as the OS itself probably does not use Java.

 > Do you know how I could change the JVM used by tomcat on a machine?

To change the JVM used by Tomcat is easy, but first you need to install a 1.6 JVM on that 
machine.  You should be able to install the JVM 1.6 "in addition to" the existing 1.5, if 
you have any concern about the possibility of breaking other applications.
For the exact way to do that, you will need help from an OS specialist for that machine.

Once you have installed this 1.6 JVM, having Tomcat use it instead of the 1.5 JVM is easy.
Basically, it consists of setting the environment value "JAVA_HOME" to point to the new 
JVM before starting Tomcat.  That's all there is to it.
That needs to be done somewhere in the scripts which are used at Tomcat start, but I 
cannot tell you where exactly on that platform.  If Java and Tomcat are IBM "packages" on 
that platform, then you will probably also need an OS specialist to help you with that.

> 
> re: your fourth point I test this by changing the system time on the O/S.
>
Right. But my point was : since in reality, on a productive system, this is happening only 
twice a year, does it matter if those times the application(s) get reloaded ?
(In fact, I strongly suspect that it may happen only /at most/ once a year, and then only 
in very specific circumstances.  It is your changing of the system time which triggers the 
reloading, but it would probably never happen in reality on a production system).

> I couldn't figure out how to test your last guess because the context element in tomcat's context.xml wouldn't accept the reloadable attribute.
> 

That was only a wild unsubstantiated guess.
I expect someone else more qualified to shoot down that suggestion, just about... now.

> Thanks,
> 
Welcome.

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