RE: Tomcat 5.5.27 - Solaris 10 - Tomcat process starts additional copies of itself with only 1 thread and no CPU

2011-09-09 Thread Dave Stubbs
hould fail, and that should normally leave a trace in the Tomcat logs. Else, they are not real processes and really are threads, no matter what "ps" is saying. You could also try taking some thread dumps of the Tomcat JVM (see the Tomcat FAQ), to see if some thread-id there match th

RE: Tomcat 5.5.27 - Solaris 10 - Tomcat process starts additional copies of itself with only 1 thread and no CPU

2011-09-09 Thread Dave Stubbs
nux, shows the ports on which processes are listening, and the corresponding PID's and maybe program name) Dave Stubbs wrote: > We're experiencing a problem on both production and test systems that > has only started to occur in the last few weeks (no new version of any >

RE: Tomcat 5.5.27 - Solaris 10 - Tomcat process starts additional copies of itself with only 1 thread and no CPU

2011-09-09 Thread Dave Stubbs
Sent: 09 September 2011 11:11 To: users@tomcat.apache.org Subject: Re: Tomcat 5.5.27 - Solaris 10 - Tomcat process starts additional copies of itself with only 1 thread and no CPU Am Fri, 9 Sep 2011 09:54:36 +0100 schrieb "Dave Stubbs" : > When we list the system tasks we see that the ghos

RE: Tomcat 5.5.27 - Solaris 10 - Tomcat process starts additional copies of itself with only 1 thread and no CPU

2011-09-09 Thread Dave Stubbs
ional copies of itself with only 1 thread and no CPU 2011/9/9 Dave Stubbs : > We are seeing tomcat starting up additional copies of itself, each new >copy is allocating a chunk of storage, it only starts 1 thread, >nothing gets written to any logs and no CPU is being listed as having

Tomcat 5.5.27 - Solaris 10 - Tomcat process starts additional copies of itself with only 1 thread and no CPU

2011-09-09 Thread Dave Stubbs
We're experiencing a problem on both production and test systems that has only started to occur in the last few weeks (no new version of any software have been put live to anyone's knowledge) that has us quite stumped. We are seeing tomcat starting up additional copies of itself, each new copy