RE: Tomcat spawns excessive jvms and kills server for jdk1.3 and jdk1.4

[will <wi...@datapro.co.uk>]

Hi,

I get the same using jdk1.3/Tomcat 4.0.4 with Caldera OpenLinux 3.1.1. I
have not had it dieing yet, but I have only just installed it, so haven't
really hammered it yet. Did you find out what the problem was?

Regards,

Wm.

-----Original Message-----

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.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.373 / Virus Database: 208 - Release Date: 01/07/2002
 

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>