tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: tomcat crash problem (INTERNAL)
Date Mon, 06 Oct 2014 08:27:07 GMT
Hi Ognjen,

Could you please suggest one best open source java profiler for analysing and monitoring the
tomcat server.


-----Original Message-----
From: Ognjen Blagojevic [] 
Sent: 3. oktober 2014 12:47
To: Tomcat Users List
Subject: Re: tomcat crash problem (INTERNAL)


On 3.10.2014 10:25, 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:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message