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 (nike.apache.org: local policy)
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Date: Wed, 25 Feb 2009 22:35:21 -0600
Subject: RE: very slow class loading on initial JSP/servlet request
 	afterrestart
Thread-Topic: very slow class loading on initial JSP/servlet request
 	afterrestart
Thread-Index: AcmXnvk3yqqqX+tQSqO2Kflwy2B//gAJJ6vQ
Message-ID: 
 <0AAE5AB84B013E45A7B61CB66943C17215B859616A@USEA-EXCH7.na.uis.unisys.com>
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>
In-Reply-To: <49A5D0D0.6050008@ims.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> From: Sam Hokin [mailto:sam@ims.net]
> Subject: Re: very slow class loading on initial JSP/servlet
> request afterrestart

> It looks like we've boiled the problem, at least in this test
> JSP case, down to the classloader wasting 3 seconds per
> try on stat-ing core Java classes in an imaginary location,
> /net/ims/jcms, on the server's filesystem, which actually
> corresponds to a path WITHIN a jar file that I wrote, and
> which doesn't contain any core Java classes.

Some comments on the above:

1) It's not a Tomcat or JVM classloader that's doing the lookup - it's the =
JDT compiler hunting for unresolved class references.

2) The Object.class, Throwable.class, etc., core class files are not known =
to be core until they *haven't* been found on any imported packages that in=
clude a wildcard.  That's why the lookups are done with a wildcard, and not=
 done with explicit classes.

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 =3D ALL

That will display a *lot* of information about what's going on during JSP c=
ompilation.  One thing in particular printed out during Tomcat initializati=
on 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.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA=
TERIAL and is thus for use only by the intended recipient. If you received =
this in error, please contact the sender and delete the e-mail and its atta=
chments from all computers.

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