tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: tomcat 7.0.29 startup time
Date Sat, 28 Jul 2012 00:36:24 GMT
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


Mime
View raw message