You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Wick Swain <ws...@axis41.com> on 2002/07/09 19:41:57 UTC
Tomcat spawns excessive jvms and kills server for jdk1.3 and jdk1.4
When we start Tomcat on our Redhat 7.2 server, it immediatly spawns 35 jvm processes (as shown by "ps -ef | grep java" command). As pages are served, more jvm processes are created until the server finally runs out of memory and dies.
The problem goes away if we use jdk1.2.2 as our JAVA_HOME (in which case only one jdk process is created and it runs great). When we use jdk1.3.1 or jdk1.4.0 the problem occurs for both Tomcat 3.x and Tomcat 4.x. There is some new functionality in jdk1.4 that we would love to use but we are now tied to jdk1.2 in order to keep Tomcat up and running.
Attached is the output of a "ps -ef | grep java" command with the JAVA_HOME set first to jdk1.3.1 and then to jdk1.2.2. The commands are run immediately after starting tomcat.
Thanks in advance for any ideas.