I don't recomend using the -server option, the server version is buggy as
hell
and crashes constantly, you will just have to wait for SUN to get their
act together.
Aymeric Alibert [EMAIL PROTECTED] wrote on 10.12.2002
22:38:19:
We are running a Tomcat 4.0 server in our production
version of Solaris??
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Aymeric Alibert [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 7:37 PM
To: [EMAIL PROTECTED]
Subject: RE: TC 4.1 and VM crash: how to report issue?
Thanks for the feedback.
When I ran my
-Original Message-
From: Aymeric Alibert [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 7:37 PM
To: [EMAIL PROTECTED]
Subject: RE: TC 4.1 and VM crash: how to report issue?
Thanks for the feedback.
When I ran my load tests I used -Xmx512m -Xms512m as heap settings.
I also
I changed the debug flag to 10 in all elements of my server.xml.
Looking at the log file, I cannot identifiy any error or warning from
Tomcat before it crashes.
Here is a sample:
...
StandardContext[/residential]: Mapped to servlet 'default' with servlet path
'/images/home_hdr.jpg' and path
Have you tried turning off the HotSpot JIT compiler and trying your
test? All other things being equal, this will show you that the problem
resides in the interaction between Tomcat and the compiled code.
Just a thought...
Ben Ricker
On Wed, 2002-12-11 at 08:44, Aymeric Alibert wrote:
I
You are right. Nothing helfull...Yoav recommendations are probably the
way to explore nowYou should file a bug and try to escalate it on
the SUN web site.
-- Jeanfrancois
Aymeric Alibert wrote:
I changed the debug flag to 10 in all elements of my server.xml.
Looking at the log file, I
, 0x66daa8, 0x8), at 0xfe58fee8
[64] _start(0xfe796000, 0xfe265d18, 0x0, 0x5, 0x1,
0xfe401000), at 0xfe57fd0c
-Original Message-
From: Aymeric Alibert [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 4:37 PM
To: [EMAIL PROTECTED]
Subject: RE: TC 4.1 and VM crash: how
We are running a Tomcat 4.0 server in our production environment and
I am trying to upgrade to Tomcat 4.1.
I ran some load test recently and was horrified to see the server crashing even
under moderate load. After more testing, I found that starting the VM with the
-server option systematically
settings.
-Manoj.
-Original Message-
From: Aymeric Alibert [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 5:38 PM
To:
Subject: TC 4.1 and VM crash: how to report issue?
We are running a Tomcat 4.0 server in our production environment and
I am trying to upgrade to Tomcat 4.1.
I
Howdy,
If your OS requires patches in order to run the JDK (whatever version
you're trying to run), make sure those patches are installed. I had
this exact issue happen on Solaris, and installing the proper Solaris
patches made it go away.
You say The same behavior can be reproduced with both
Aymeric Alibert wrote:
We are running a Tomcat 4.0 server in our production environment and
I am trying to upgrade to Tomcat 4.1.
I ran some load test recently and was horrified to see the server crashing even
under moderate load. After more testing, I found that starting the VM with the
Thanks for the feedback.
When I ran my load tests I used -Xmx512m -Xms512m as heap settings.
I also tried increasing or decreasing it but it didn't change the
results.
I am running on Solaris and I have all the recommended patches for
JDK1.4.1 installed.
I can reproduce the problem: it is
Have you try running your test and verbosing as much as possible
information inside the log file (increase the debug level in
server.xml)? Try it to see if Tomcat 4.1.x output something useful to
trace the problem. Post your result (ot the last couple of lines). Maybe
it will help.
--
13 matches
Mail list logo
