tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46264] Shutting down tomcat with large number of contexts is slow
Date Thu, 13 Oct 2011 14:41:42 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46264

--- Comment #23 from Felix Schumacher <felix.schumacher@internetallee.de> 2011-10-13
14:41:42 UTC ---
With core pool size set to "0" in ContainerBase#initInternal I get no
concurrency at startup. It will be sequential only. If I change it back to 

  startStopExecutor = new ThreadPoolExecutor(getStartStopThreadsInternal(),
                getStartStopThreadsInternal(), 10, TimeUnit.SECONDS,
                startStopQueue);

I get a concurrent startup. (Startup time for my 20 dummy applications go down
from 16s to 9s)


As ContainerBase#initInternal is also called from StandardContext, each Context
will get its own startStopExecutor. Is this really needed?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


Mime
View raw message