re it had a problem.
Thanks,
Carl
- Original Message -
From: "Pid"
To:
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 it cycled afte
u search the OS logs for evidence of an
OOM kill?
cat /var/log/messages | grep --ignore-case "killed process"
p
- Original Message - From: "David kerber"
To: "Tomcat Users List"
Sent: Thursday, January 14, 2010 8:48 AM
Subject: Re: Tomcat dies sudde
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 the memTest sugges
2010/1/14 David kerber :
> 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 to the +
version w
. Probably call Dell this morning.
TIA,
Carl
- Original Message - From: "David Kerber"
To: "Tomcat Users List"
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 :
Make sur
ednesday, January 13, 2010 6:26 PM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
Peter Crowther wrote:
2010/1/13 David kerber :
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 usua
Peter Crowther wrote:
2010/1/13 David kerber :
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
-
2010/1/13 David kerber :
> 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
---
David,
Will do... thanks for the heads up.
Carl
- Original Message -
From: "David kerber"
To: "Tomcat Users List"
Sent: Wednesday, January 13, 2010 1:17 PM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
Carl wrote:
Peter,
The memTest is still runn
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: users-unsubs
Peter,
The memTest is still running but clean so far.
Thanks,
Carl
- Original Message -
From: "Peter Crowther"
To: "Tomcat Users List"
Sent: Wednesday, January 13, 2010 12:00 PM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
2010/1/13 Christopher Schul
opher Schultz"
To: "Tomcat Users List"
Sent: Wednesday, 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 di
2010/1/13 Christopher Schultz :
> 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 physical me
-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 t
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 of memory, you hav
In process... thanks for the suggestion.
Carl
- Original Message -
From: "Peter Crowther"
To: "Tomcat Users List"
Sent: Wednesday, January 13, 2010 8:49 AM
Subject: Re: Tomcat dies suddenly (was JVM goes away)
Very difficult to know what the problem is. One
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 ex
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 mem
>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 HotSpot(
constrained perm gen, etc.)
Thanks,
Carl
- Original Message -
From: "Pid"
To: "Carl"
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
hea
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
to the edge that I don't see it. Odd though,
I have forced OOM issues in the past and they always showed up in
catalina.out.
Thanks for your thoughts and help.
Carl
- Original Message -
From: "Pid"
To:
Sent: Monday, January 11, 2010 8:07 PM
Subject: Re: JVM goes a
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 held (as seen
from top) b
;Tomcat Users List"
Sent: Monday, January 11, 2010 7:31 PM
Subject: Re: JVM goes away
2010/1/12 Carl :
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 le
2010/1/12 Carl :
> 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 above are
M is or is not running as a daemon?
TIA,
Carl
- Original Message -
From: "Andy Wang"
To:
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
g but saw nothing that looked out of the ordinary.
>
> I will cut back on the heap and permgen tonight (gonna be a long one.)
>
> Any ideas are welcome.
>
> Thanks,
>
> Carl
>
>
> - Original Message ----- From: "Peter Crowther"
>
> To: "Tom
2010 6:06 PM
Subject: Re: JVM goes away
2010/1/11 Carl :
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 Environ
in any log (Tomcat or
> system) 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 J
#x27;s, etc. at a
> reasonable speed. Without warning and with no tracks in any log (Tomcat or
> system) 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
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 physical memory.
The applicati
31 matches
Mail list logo
