> That sounds possible. (I haven't looked at the code to check the theory
> though.)
>
> Please open a Bugzilla issue for this so it doesn't get lost.
thanks for your reply. I filed a bug for Tomcat 8:
https://issues.apache.org/bugzilla/show_bug.cgi?id=57472
> I assume your web application is load
Hi,
After moving one of our web applications from Tomcat 7 to Tomcat 8 (latest
8.0.17) the time for deploying and initializing the webapp increased by a
factor of 30 (6s vs. 180s). Analyzing the problem we found out that it had to
do with a signed jar in the WEB-INF/lib of the webapp. It is a 8
> -Ursprüngliche Nachricht-
> Von: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
> Gesendet: Freitag, 17. August 2012 15:50
> An: Tomcat Users List
> Betreff: Re: hostConfigClass attribute
>
> 2012/8/16 Schulz-Hildebrandt, Ole :
> > Hi,
> >
>
Best regards,
Ole
-Ursprüngliche Nachricht-
Von: Mark Thomas [mailto:ma...@apache.org]
Gesendet: Donnerstag, 16. August 2012 17:40
An: Tomcat Users List
Betreff: Re: hostConfigClass attribute
On 16/08/2012 16:03, Schulz-Hildebrandt, Ole wrote:
> Hi,
>
> I'm working with tomcat
Hi,
I'm working with tomcat 7.0.29. In tomcat 5.x.x it was possible to use a custom
HostConfig class by setting the hostConfigClass attribute at a element
in the server.xml. This allowed to customize the order webapps were started, to
avoid deploying of webapps at tomcat startup etc. Though th
