"Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
> Indeed, a thread dump after the shutdown command is executed shows a bunch
> of active threads, including those suspended by a wait() at:
> org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:
> 407)
> org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:
> 495)
> org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:
> 495)
> org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:
> 495)
Do we still really need a thread pool? I believe that the major
pain-in-the-neck (Linux) will go away once 2.4.19 gets out of the door once
IBM's code get into there (has been approved)...
Solaris does thread-pooling already in kernel, and windows (oh well, let's
just dump it), I don't know...
Any performance ideas (latest stats I've seen are of several years ago,
Jserv time)...
Pier
--
I think that it's extremely foolish to name a server after the current U.S.
President. B.W. Fitzpatrick
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
