tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Tomcat slow during startup >= 7.0.28
Date Tue, 15 Jan 2013 21:46:47 GMT
Hash: SHA256


On 1/15/13 4:58 AM, Conrad Kostecki wrote:
> Hi Chris!
> Am 14.01.2013 16:44, schrieb Christopher Schultz:
>> [..] Take a thread dump or two. I suspect that Tomcat is scanning
>> more JAR files than it used to due to the clarifications of
>> certain behaviors by the servlet EG. If Tomcat is spending a long
>> time scanning JAR files, there are a number of ways to stop that
>> from happening. Let's confirm before we start changing
>> configuration, though.
> I am attaching you both dumps: Dump1:
> [Tomcat 7.0.32]

This thread dump clearly shows that annotations are being processed by
the thread called "localhost-startStop-1". If it really takes several
minutes to continue form this point, you should be able to take a few
more thread dumps and see that it's still performing annotation

I think it's clear that's what the problem is.

> Dump2: [Tomcat 7.0.26]

I'm not sure what I'm supposed to learn from that thread dump, as you
said it didn't have a problem. The only thing going on in there is
that Spring is initializing itself.

In order to disable annotation processing, you should set
metadata-complete="true" on your <web-app> element. Note that this
attribute in only valid in servlet-spec 2.5 and later deployment
descriptors, so if you're stuck on 2.4, 2.3 or something even older
than that, it's really time to upgrade.

(I'll have to check, but recently the servlet EG made some
clarifications about backward (in)compatibility that seemed ...
surprising. I'll have to re-read what those were to see if they will
affect JAR scanning.)

- -chris
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools -
Comment: Using GnuPG with undefined -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message