Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 57515 invoked from network); 7 Oct 2010 20:35:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Oct 2010 20:35:15 -0000 Received: (qmail 4137 invoked by uid 500); 7 Oct 2010 20:35:11 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 3942 invoked by uid 500); 7 Oct 2010 20:35:11 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 3933 invoked by uid 99); 7 Oct 2010 20:35:11 -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 20:35:11 +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 20:35:04 +0000 Received: from [192.168.245.129] (p549E24A7.dip0.t-ipconnect.de [84.158.36.167]) by tor.combios.es (Postfix) with ESMTPA id C9A0422654A for ; Thu, 7 Oct 2010 22:31:17 +0200 (CEST) Message-ID: <4CAE2ECB.4050809@ice-sa.com> Date: Thu, 07 Oct 2010 22:34:19 +0200 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Disable class monitoring for reloading container classes References: <4CACDD1B.4000103@ice-sa.com> <4CADA039.7090409@ice-sa.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Jane Muse wrote: .. > The reason why there's a problem when the application gets reloaded is due to we are loading a JNI native library that the application requires. According to the following link, section 11.2.4, the JVM does not allow a JNI native library to be loaded by more than one class loader. When the application is shut down by tomcat, the native library does not get unloaded from the class loader. This only happens when the JVM is brought down. Thus when the application starts up after tomcat reloads it, we get an UnsatisfiedLinkError. > Ok, I can really not comment on that one. It seems a valid reason to me, but I am by no means a specialist here. > There are several Java's on the IBM machine. Yesterday I performed tests by changing JAVA_HOME in the catalina startup script to Sun's Java 1.5 and Sun's java 1.6. Previously it was IBM's J9 1.5.0. The results were the same with the various JVM's. > Are you sure that wherever you changed it, is really being used ? If you go to the "bin" directory of your Tomcat installation, and execute the "./version.sh" script, what does it tell you ? The reason I am asking, is that when Tomcat comes "pre-packaged" for some given OS, the packagers may have provided their own startup scripts, which may not use the standard Tomcat startup scripts, or which may overwrite the "JAVA_HOME" environment value before actually launching Tomcat. We on this list generally do not know the exact contents of these packages, so you really have to make sure, by following the chain of what happens when you start Tomcat on that machine. If you know where the line is which actually launches Tomcat, you could insert an instruction just before, such as echo "Java Home : $JAVA_HOME" just to make sure. And there is always the workaround mentioned by Pid.. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org