Linux is the problem here. As you increase the mx JVM flag to be, the number of
threads the java process can create decreases. This
not a tomcat thing but a java on linux thing. For example, setting mx to be 1028
MBytes results in a thread ceiling of something
like 427, which is really low for a
Has anybody noticed that as you increase the -mx while running tomcat on
linux, the maximum number of threads decreases?
We have run tomcat on Debian linux with 2GB of real memory and we set a
run-time flag of -mx1024m. In this configuration, once the java process
reaches a certain number of thre
Sorry for the noise)
If I'm going to go to that size I'd rather run Oracle. But if it's
something
small hypersonic is great.
--mikej
-=-
mike jackson
[EMAIL PROTECTED]
> -Original Message-
> From: Ryan Chambers [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, Fe
For an industrial strength open-source DB, try
http://postgresql.org
-Original Message-
From: Mike Jackson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 18, 2003 11:14 AM
To: Tomcat Users List; Jens Skripczynski
Subject: RE: [OT] free Database with Transaction (Sorry for the noise)
To force a dump of the call stack, type:
kill -3
I'm not sure where the output will go for you, it depends on the
configuration of your system. Search for Thread- in your log files.
As for the CPU pinning, I agree with whoever wrote in earlier that it's
probably some bad code that you wrote. Wh
Here is a contrary point of view.
They have nothing close to the same level of functionality. Tomcat is a JSP
and servlet container. Weblogic can do these things, but it is also an EJB
container, RMI server, insert list of features here.
In some cases it makes sense to integrate tomcat with webl
