tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kees Jan Koster <kjkos...@gmail.com>
Subject Re: Tomcat dies suddenly
Date Thu, 04 Feb 2010 05:47:22 GMT
Dear Carl,

So this problem happens on one machine or on more than one? If it is  
limited to one machine, I would be inclined to run memtest86 on it to  
see if the RAM is good.

Kees Jan

On 4 feb 2010, at 02:07, "Carl" <carl@etrak-plus.com> wrote:

> Chris,
>
> Interesting idea.  I tried over the weekend to force that situation  
> with JMeter hitting a simple jsp that did some data stuff and  
> created a small display.  I pushed it to the point that there were  
> entries in the log stating it was out of memory (when attempting to  
> GC, I think) but it just slowed way down and never crashed.  I could  
> see from VisualJVM that it had used the entire heap but, again, I  
> could never get it to crash.
>
> Strange because it doesn't have the classic signs (slowing down or  
> throwing out of memory exceptions or freezing), it just disappears  
> without any tracks.  I am certain there is a reason somewhere, I  
> just haven't found it yet.
>
> Thanks for your suggestions,
>
> Carl
>
> ----- Original Message ----- From: "Christopher Schultz" <chris@christopherschultz.net

> >
> To: "Tomcat Users List" <users@tomcat.apache.org>
> Sent: Wednesday, February 03, 2010 5:45 PM
> Subject: Re: Tomcat dies suddenly
>
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Chuck,
>>
>> On 2/3/2010 5:00 PM, Caldarale, Charles R wrote:
>>>> From: Carl [mailto:carl@etrak-plus.com]
>>>> Subject: Re: Tomcat dies suddenly
>>>
>>>> I am hoping I can see failure at the point of failure
>>>> with the heap dump options
>>>
>>> That won't have any effect on the Linux OOM killer.  If it is the  
>>> OOM killer taking out Tomcat, the JVM will not receive any  
>>> notification - all threads will just be terminated with extreme  
>>> prejudice.  There won't be a chance for the heap dump to happen.
>>
>> Maybe what Carl should try is to actually cause an OOME without
>> triggering the "OOM Killer".
>>
>> Carl: you said that everything is copacetic when you run with a  
>> smaller
>> heap, right? Well, run with that smaller heap, but then write a  
>> simply
>> servlet/JSP/whatever that just allocates huge, say, byte[] buffers  
>> until
>> it gets an OOME and verify that you get a heap dump when that  
>> happens.
>>
>> - -chris
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (MingW32)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAktp/JEACgkQ9CaO5/Lv0PBI0ACgmDLJVxM5xDiN5UIFsqqKRj7i
>> 2J8AoL8ENGsYxwudtFrLy+tZTzmr/rxC
>> =4yC9
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message