@tomcat.apache.org
Sent: Wednesday, January 13, 2010 6:26 PM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
Peter Crowther wrote:
2010/1/13 David kerber dcker...@verizon.net:
Make sure you let it run for quite a while. I've had memory failures
show
up as late as 11 passes into a test run
. Probably call Dell this morning.
TIA,
Carl
- Original Message - From: David Kerber dcker...@verizon.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, January 13, 2010 6:26 PM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
Peter Crowther wrote:
2010/1/13 David
2010/1/14 David kerber dcker...@verizon.net:
Memtest86, which I believe is the same one Peter suggested (or at least a
variation of it). It just loops continuously until stopped.
I suggested memtest86+ (http://www.memtest.org/). Memtest86
(http://www.memtest86.com/) is also available; I moved
: Thursday, January 14, 2010 8:48 AM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
Memtest86, which I believe is the same one Peter suggested (or at least a
variation of it). It just loops continuously until stopped.
Carl wrote:
David,
What do you use for your mem testing?
I am using
(was JVM goes away)
Memtest86, which I believe is the same one Peter suggested (or at
least a variation of it). It just loops continuously until stopped.
Carl wrote:
David,
What do you use for your mem testing?
I am using the memTest suggested by Peter... after six tests, it
still shows all
it had a problem.
Thanks,
Carl
- Original Message -
From: Pid p...@pidster.com
To: users@tomcat.apache.org
Sent: Thursday, January 14, 2010 9:55 AM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
On 14/01/2010 14:36, Carl wrote:
David,
I am such a dufuss... didn't even notice
From the original posting:
This is a new server, a Dell T110 with a Xeon 3440 processor and 4GB memory. I
have turned off both the turbo mode and hyperthreading.
The environment:
64 bit Slackware Linux
java version 1.6.0_17
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java
Very difficult to know what the problem is. One thing you can now do
(as you've switched to another production server) is to run a memory
test across the bad server. A T110 doesn't use error-correcting
memory, as I recall, so a dodgy bit could cause problems. Give it a
couple of hours with
In order to monitor java memory at chrash time you can add to JAVA_OPTS
these directives
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/your/tomcat/folder/memorydump.hprof
In this way, if tomcat goes in out of memory, you have an image of memory
(memorydump.hprof) that you can analyze by an
In process... thanks for the suggestion.
Carl
- Original Message -
From: Peter Crowther peter.crowt...@melandra.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, January 13, 2010 8:49 AM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
Very difficult to know
, January 13, 2010 8:58 AM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
In order to monitor java memory at chrash time you can add to JAVA_OPTS
these directives
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/your/tomcat/folder/memorydump.hprof
In this way, if tomcat goes in out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 1/13/2010 8:49 AM, Peter Crowther wrote:
Very difficult to know what the problem is. One thing you can now do
(as you've switched to another production server) is to run a memory
test across the bad server.
Usually, I would agree that
2010/1/13 Christopher Schultz ch...@christopherschultz.net:
On 1/13/2010 8:49 AM, Peter Crowther wrote:
Very difficult to know what the problem is. One thing you can now do
(as you've switched to another production server) is to run a memory
test across the bad server.
Usually, I would
, January 13, 2010 11:50 AM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 1/13/2010 8:49 AM, Peter Crowther wrote:
Very difficult to know what the problem is. One thing you can now do
(as you've switched to another production
Peter,
The memTest is still running but clean so far.
Thanks,
Carl
- Original Message -
From: Peter Crowther peter.crowt...@melandra.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, January 13, 2010 12:00 PM
Subject: Re: Tomcat dies suddenly (was JVM goes away
Carl wrote:
Peter,
The memTest is still running but clean so far.
Make sure you let it run for quite a while. I've had memory failures
show up as late as 11 passes into a test run.
D
-
To unsubscribe, e-mail:
David,
Will do... thanks for the heads up.
Carl
- Original Message -
From: David kerber dcker...@verizon.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, January 13, 2010 1:17 PM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
Carl wrote:
Peter
2010/1/13 David kerber dcker...@verizon.net:
Make sure you let it run for quite a while. I've had memory failures show
up as late as 11 passes into a test run.
That's dedication - I usually end up stopping it after a couple of
runs. Thanks David, I've learned something!
- Peter
Peter Crowther wrote:
2010/1/13 David kerber dcker...@verizon.net:
Make sure you let it run for quite a while. I've had memory failures show
up as late as 11 passes into a test run.
That's dedication - I usually end up stopping it after a couple of
runs. Thanks David, I've learned
-plus.com
Sent: Tuesday, January 12, 2010 4:41 AM
Subject: Re: JVM goes away
On 12/01/2010 01:30, Carl wrote:
Aha, for some reason, I thought perm gen was included in the general
heap so the maximum for the two combined was constrained by the 2400m I
had defined for the heap. Somewhere around 2:00AM (I
constrained perm gen, etc.)
Thanks,
Carl
- Original Message -
From: Pid p...@pidster.com
To: Carl c...@etrak-plus.com
Sent: Tuesday, January 12, 2010 4:41 AM
Subject: Re: JVM goes away
On 12/01/2010 01:30, Carl wrote:
Aha, for some reason, I thought perm gen was included
for only several hours. Initially, I
thought the problem was the turbo or hyperthreading but, no, the problem
persists.
When the JVM goes away, the memory that it held is still being held (as seen
from top) but it is nowhere near the machine physical memory.
The application has been running
) or to the console, the JVM will just go away, disappear. Sometimes,
the system will run for a week, sometimes for only several hours. Initially,
I thought the problem was the turbo or hyperthreading but, no, the problem
persists.
When the JVM goes away, the memory that it held is still being
,
the system will run for a week, sometimes for only several hours. Initially,
I thought the problem was the turbo or hyperthreading but, no, the problem
persists.
When the JVM goes away, the memory that it held is still being held (as seen
from top) but it is nowhere near the machine
Sent: Monday, January 11, 2010 6:06 PM
Subject: Re: JVM goes away
2010/1/11 Carl c...@etrak-plus.com:
This is a new server, a Dell T110 with a Xeon 3440 processor and 4GB
memory. I have turned off both the turbo mode and hyperthreading.
The environment:
64 bit Slackware Linux
java version
(gonna be a long one.)
Any ideas are welcome.
Thanks,
Carl
- Original Message - From: Peter Crowther
peter.crowt...@melandra.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, January 11, 2010 6:06 PM
Subject: Re: JVM goes away
2010/1/11 Carl c...@etrak-plus.com
,
Carl
- Original Message -
From: Andy Wang aw...@ptc.com
To: users@tomcat.apache.org
Sent: Monday, January 11, 2010 6:42 PM
Subject: Re: JVM goes away
I assume $GB means 4GB :)
With that kind of memory use it doesn't sound entirely like the OOM
killer. Have you looked around
2010/1/12 Carl c...@etrak-plus.com:
Peter and Andy,
Thanks for your quick responses.
Memory: Physical - $GB
Used - 2.4GB to 3.0 GB (according to top... have never seen it
above 3GB)
Swap - 19GB, none ever used (or, at least I have never seen
any used.)
The
Users List users@tomcat.apache.org
Sent: Monday, January 11, 2010 7:31 PM
Subject: Re: JVM goes away
2010/1/12 Carl c...@etrak-plus.com:
Peter and Andy,
Thanks for your quick responses.
Memory: Physical - $GB
Used - 2.4GB to 3.0 GB (according to top... have never seen it
above 3GB)
Swap - 19GB
go away, disappear. Sometimes,
the system will run for a week, sometimes for only several hours. Initially, I
thought the problem was the turbo or hyperthreading but, no, the problem
persists.
When the JVM goes away, the memory that it held is still being held (as seen
from top
Subject: Re: JVM goes away
On 11/01/2010 23:06, Peter Crowther wrote:
2010/1/11 Carlc...@etrak-plus.com:
This is a new server, a Dell T110 with a Xeon 3440 processor and 4GB
memory. I have turned off both the turbo mode and hyperthreading.
The environment:
64 bit Slackware Linux
java version
31 matches
Mail list logo
