Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates
 212.85.38.174 as permitted sender)
Message-ID: <49A6D31F.2030409@ice-sa.com>
Date: Thu, 26 Feb 2009 18:36:31 +0100
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: very slow class loading on initial JSP/servlet request after
 restart
References: <499DEA05.4040501@ims.net>
 			<499EB1D6.7020302@christopherschultz.net> <499ED728.4080909@ims.net>
 		<0AAE5AB84B013E45A7B61CB66943C17215B8312EDE@USEA-EXCH7.na.uis.unisys.com>
 		<499EE439.2060102@ims.net> <499EF07B.8050607@christopherschultz.net>
 		<499EF641.30403@ims.net> <499EF835.2060907@cornell.edu>
 		<499F38A8.3060503@christopherschultz.net> <499F404E.7030107@ims.net>
 		<499F41BD.5010701@apache.org> <49A44251.10506@ims.net>
 		<49A5129A.6040806@apache.org> <49A58212.9000507@ice-sa.com>
 		<49A59269.3040609@ims.net> <49A5BE0A.300@ims.net>
 	<0AAE5AB84B013E45A7B61CB66943C17215B8595ED5@USEA-EXCH7.na.uis.unisys.com>
 <49A5D0D0.6050008@ims.net>
 <0AAE5AB84B013E45A7B61CB66943C17215B859616A@USEA-EXCH7.na.uis.unisys.com>
 <49A6C3D3.5010604@ims.net>
In-Reply-To: <49A6C3D3.5010604@ims.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sam Hokin wrote:
> Caldarale, Charles R wrote:
>> Once you have your test Tomcat set up on the problematic server, try 
>> adding this line to the conf/logging.properties file:
>>
>> org.apache.jasper.level = ALL
>>
>> That will display a *lot* of information about what's going on during 
>> JSP compilation.  One thing in particular printed out during Tomcat 
>> initialization is the compiler classpath for JSPs in each webapp, 
>> which might show why the lookups are being done at the root of the 
>> file system.
> 
> OK, done.  I started up my test instance, ran a single request on my 
> test JSP, and shut it down.  The resulting
> catalina.out is here for your review:
> 
> http://ims.net/media/jasper-level-all.txt
> 
> Sure enough, / appears in the classpath for the ROOT webapp, right here:
> 
> [stuff]:/usr/local/lib/jtds-1.2.2.jar:/:/usr/local/tomcat-2/bin/bootstrap.jar:[other 
> stuff]
> 
> / is appended after a jar that I have symlinked under $TOMCAT_HOME/lib 
> and before bootstrap.jar.

and, this is also maybe where these lstat calls were coming from (lstat 
varies from stat in that it queries the symlink itself, rather than the 
underlying real file).

> 
> So, SINCE my company is ims.net and my Java packages start with net.ims; 
> and SINCE I had autofs running which
> automounted /net; and SINCE / is in the classpath, JDT searched under 
> /net to find core classes, which incurred a very
> long delay, presumably due to automount.  If autofs is off and /net is 
> simply an empty directory, the delay is not
> incurred.  My problem is cured by simply turning off autofs.
> 
> It seems to me that it's a bug that / is being appended to the 
> classpath, but one that didn't result in pain until the
> particular circumstance above came into play, clearly a VERY specific 
> scenario.
> 
> THANKS, EVERYONE! I think we've solved this riddle! I owe you all beers, 
> or your beverage of choice!
> 
My preferred one is Westvleteren, arguably the best beer in the world.
See http://en.wikipedia.org/wiki/Westvleteren_Brewery
Cheap, but hard to get.
You can have it delivered at the ApacheCON Europe 2009, and I will take 
care of the distribution to deserving contributors.  Maybe we can even 
get some to Minnesota, along with some Belgian dark chocolate.

I am very glad that this turned out after all as a (fruitful) 
intellectual pursuit, rather than a boring hardware issue.


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