tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yogesh Rao <yog...@gmail.com>
Subject Re: tomcat crash problem (INTERNAL)
Date Sun, 05 Oct 2014 15:38:26 GMT
Subbu,

You either could analyse the applications heap usage as ognjen suggested or
If possible try deploying the application with the latest release of tomcat
6 (6.0.41) . There could have been patches released which could have fixed
the issue.

Regards,
-Yogesh

On Fri, Oct 3, 2014 at 4:17 PM, Ognjen Blagojevic <
ognjen.d.blagojevic@gmail.com> wrote:

> Subbu,
>
> On 3.10.2014 10:25, Bala-Subrahmanyam.Bhatta@telenor.com wrote:
>
>> Hi Ognjen,
>>
>> Tomcat is crashing with the below error message.
>>
>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>
>
> Please, reply below the quotes, it is standard on this list.
>
> Tomcat have small memory footprint, way below 3 GB you allocate for JVM.
> So, it is probably your application data filling this 3 GB of memory. The
> above error says that garbage collector is struggling to release the
> memory, but it consumes to much CPU cycles and releases too little memory.
> This usually results in dramatic server slowdowns, so JVM decides to throw
> an error and inform you about the problem.
>
> You should analyze your application heap usage with the profiler to
> determine what objects are holding references so GC is unable to free more
> memory. If you don't need those objects, clear the references. If you
> really need all those objects, throw more memory at the server.
>
> Please read:
>
>   http://wiki.apache.org/tomcat/OutOfMemory
>
>
> -Ognjen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message