tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Fourel" <>
Subject Re: Tomcat 5.5 hanged . Thread Dump Analyze
Date Wed, 16 Jul 2008 07:07:54 GMT
Thank you a lot for your analyze and your help.
I will study the link you gave.

If it is a memory link problem, I assume we could easily reproduce the
problem with a script that would generate a lot of load on our serveur.
In such a case, we could in few minutes reproduce the case.

What do you think ?


On Wed, Jul 16, 2008 at 4:38 AM, Caldarale, Charles R <> wrote:

> > From: Olivier Fourel []
> > Subject: Tomcat 5.5 hanged . Thread Dump Analyze
> >
> > our Tomcat production server hanged again.
> > We made 2 thread dumps with few minutes between them.
> The only thing I found suspicious is that PermGen is at 99% in both of
> them.  (You also have a tonne of non-Tomcat threads running around, but none
> appear hung; I presume your webapps created these and will dispose of them
> properly at an appropriate time.)
> If you are filling up the PermGen, you should be getting log entries for
> the OOMEs being thrown - unless something in your webapps is catching them
> and throwing them away.  PermGen exhaustion is frequently caused by poor
> application design, hanging on to references to classes that should be
> discarded.  This link (from the Tomcat FAQ) contains some interesting
> comments:
> You might try increasing the PermGen size, but that is likely only to delay
> the inevitable until you fix the memory leak.  You can monitor the PermGen
> growth with JConsole with little impact on performance.
>  - Chuck
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
> ---------------------------------------------------------------------
> To start a new topic, e-mail:
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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