I encountered a similar issue of numerous Httpd processes spawning b/c of Tomcat. The issue for me was that Tomcat was running out of memory, and Httpd for some reason thought spawning a bunch a threads would help ;)
Do you know how much memory these instances of Tomcat are using? The default JVM memory is ridiculously low and requires the adjustment to higher maximum value for production servers. Grep "heap" catalina.out to see if tomcat is indeed running out of memory. On Wed, Jun 10, 2009 at 12:44 PM, Peter Crowther < peter.crowt...@melandra.com> wrote: > OK, so that's a JRockit JVM, not a Sun JVM. Remind me not to point you at > any more Sun documentation! > > As a rough look at that, there are a few threads in the HTTP connector > thread pool, a bunch of threads reading data from JK connections, and one or > two in your app code. I've never looked at the innards of JK, so will have > to leave that to one of the JK experts to interpret. > > - Peter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
