Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Message-ID: <50133408.7080105@apache.org>
Date: Sat, 28 Jul 2012 01:36:24 +0100
From: Mark Thomas <markt@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: tomcat 7.0.29 startup time
References: <1343232003.41667.YahooMailNeo@web28902.mail.ir2.yahoo.com>
 <50132374.6020503@apache.org>
In-Reply-To: <50132374.6020503@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 28/07/2012 00:25, Mark Thomas wrote:
> On 25/07/2012 17:00, Mark Struberg wrote:
>> Hi Lords and Ladies!
>>
>> I'm currently wrangling with a doubled boot time on tomcat7.0.29 in
>> comparison to 7.0.28 (12 webapps in my tc: 7.0.28 < 45s, 7.0.29 >
>> 90s).
>>
>> I'm aware that 7.0.29 now does the scanning for
>> ServletContainerInitializer even if version=2.5 is specified. But
>> there shall no class scanning be performed if
>> metadata-complete="true" is set, right?
> 
> Wrong. I don't like this but the intent of the Servlet 3.0 EG was:
> - ServletContainerInitializer cannot be disabled
> - If a ServletContainerInitializer is found, then class-scanning will
> take place
> 
>> Any ideas how we can ease the pain quickly?
> 
> The only option I see is a custom (non-spec compliant) Tomcat specific
> feature that disables all of this.

Ah. See the latest developments on
http://java.net/jira/browse/SERVLET_SPEC-36

Using an absolute ordering that specifies no fragments along with
metadata-complete=true should do the trick.

Mark


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