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 15:01:23 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46264

--- Comment #24 from Mark Thomas <markt@apache.org> 2011-10-13 15:01:23 UTC ---
(In reply to comment #23)
> 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)

I'll take another look at that.

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

It isn't used at the moment and is likely to stay that way.

-- 
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