You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Robby Pelssers <rp...@agp.nl> on 2007/05/22 15:35:17 UTC
Problem with tuning JVM (high CPU load)
Hi all,
we have cocoon2.1.10 running on a solaris(OS version5.8). The server has 16G of memory and 2 processors (sparcv9 processors operating at 900 MHz). Cocoon is running on tomcat/4.1.24.
After a while we see our CPU increasing to about 94% and the system becomes non-responsive. Could anybody point to what we look for? We can't trace the problem back from the tomcat loggings.
Cheers,
Robby Pelssers
Re: Problem with tuning JVM (high CPU load)
Posted by johnson <jo...@erp.tw>.
You can check the size of log file, If it grow too fast, your sitemap
had a loop.
johnson
Robby Pelssers ??:
>
> Hi all,
>
> we have cocoon2.1.10 running on a solaris(OS version5.8). The server
> has 16G of memory and 2 processors (sparcv9 processors operating at
> 900 MHz). Cocoon is running on tomcat/4.1.24.
>
> After a while we see our CPU increasing to about 94% and the system
> becomes non-responsive. Could anybody point to what we look for? We
> can't trace the problem back from the tomcat loggings.
>
> Cheers,
> Robby Pelssers
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: Problem with tuning JVM (high CPU load)
Posted by Robby Pelssers <rp...@agp.nl>.
Hi Ralph,
We are indeed running in a 64 bit JVM. Thanks for the tip. Anyway, as
soon as we discover what is causing this problem, I will feedback to
this list!!
Robby
-----Oorspronkelijk bericht-----
Van: Ralph Goers [mailto:Ralph.Goers@dslextreme.com]
Verzonden: woensdag, mei 2007 9:06
Aan: users@cocoon.apache.org
Onderwerp: Re: Problem with tuning JVM (high CPU load)
Robby Pelssers wrote:
>
> Hi all,
>
> we have cocoon2.1.10 running on a solaris(OS version5.8). The server
> has 16G of memory and 2 processors (sparcv9 processors operating at
> 900 MHz). Cocoon is running on tomcat/4.1.24.
>
> After a while we see our CPU increasing to about 94% and the system
> becomes non-responsive. Could anybody point to what we look for? We
> can't trace the problem back from the tomcat loggings.
>
> Cheers,
> Robby Pelssers
>
Are you running in a 64 bit JVM? If not, then you aren't using much of
that 16G. However, I doubt the amount of memory has much to do with
this.
I experienced something similar to this a year and a half ago.
Periodically a thread would go into a loop. We had several problems that
made the problem diagnosis difficult.
The way our operations folks handled this was they wrote scripts that
were able to detect when a cpu suddenly spiked and when that happened
they immediately did a kill -3 to get a java dump and then killed the
application and restarted it. Once the other problems were fixed it was
easy to tell what the real problem was as that stack trace always showed
up in the thread dump.
HTH
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problem with tuning JVM (high CPU load)
Posted by Ralph Goers <Ra...@dslextreme.com>.
Robby Pelssers wrote:
>
> Hi all,
>
> we have cocoon2.1.10 running on a solaris(OS version5.8). The server
> has 16G of memory and 2 processors (sparcv9 processors operating at
> 900 MHz). Cocoon is running on tomcat/4.1.24.
>
> After a while we see our CPU increasing to about 94% and the system
> becomes non-responsive. Could anybody point to what we look for? We
> can't trace the problem back from the tomcat loggings.
>
> Cheers,
> Robby Pelssers
>
Are you running in a 64 bit JVM? If not, then you aren't using much of
that 16G. However, I doubt the amount of memory has much to do with this.
I experienced something similar to this a year and a half ago.
Periodically a thread would go into a loop. We had several problems that
made the problem diagnosis difficult.
The way our operations folks handled this was they wrote scripts that
were able to detect when a cpu suddenly spiked and when that happened
they immediately did a kill -3 to get a java dump and then killed the
application and restarted it. Once the other problems were fixed it was
easy to tell what the real problem was as that stack trace always showed
up in the thread dump.
HTH
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problem with tuning JVM (high CPU load)
Posted by Thomas Markus <t....@proventis.net>.
6g free system or jvm memory? which jvm version?
maybe that article is interesting
http://java.sun.com/developer/technicalArticles/Programming/turbo/
Robby Pelssers schrieb:
> Hi Thomas,
>
> The behaviour we see is that the CPU load gradually increases and at a
> certain point never goes down while we don't see much action taking
> place when monitoring the apache server-status. Also we still have
> around 6G free memory at the time that the CPU remains at about 94%
> load. Heap Size boundaries are Xms=12G=Xmx.
>
> Cheers,
>
RE: Problem with tuning JVM (high CPU load)
Posted by Robby Pelssers <rp...@agp.nl>.
Hi Thomas,
The behaviour we see is that the CPU load gradually increases and at a
certain point never goes down while we don't see much action taking
place when monitoring the apache server-status. Also we still have
around 6G free memory at the time that the CPU remains at about 94%
load. Heap Size boundaries are Xms=12G=Xmx.
Cheers,
Robby
-----Oorspronkelijk bericht-----
Van: Thomas Markus [mailto:t.markus@proventis.net]
Verzonden: woensdag, mei 2007 9:59
Aan: users@cocoon.apache.org
Onderwerp: Re: Problem with tuning JVM (high CPU load)
if your free memory is low, the jvm runs the gc automatically. in case
your free memory is very low the gc runs very often and consumes a lot
of cpu. try to log your current memory state in that situation.
Robby Pelssers schrieb:
> Hi Thomas,
>
> Actually, we scheduled the garbage collector as a cron job to run
every
> day at night between 2 and 3 o'clock two times to make sure memory is
> freed up when daily operations start again around 7-8 o'clock. I
don't
> really see how running the garbage collector can have a negative
affect?
> And even if there is a memory leak, how do you explain the high CPU
> load?
>
> Cheers,
> Robby
>
> -----Oorspronkelijk bericht-----
> Van: Thomas Markus [mailto:t.markus@proventis.net]
> Verzonden: woensdag, mei 2007 9:26
> Aan: users@cocoon.apache.org
> Onderwerp: Re: Problem with tuning JVM (high CPU load)
>
> Hi,
>
> looks like a memory leak. maybe the garbage collector runs very often
>
> thomas
>
>
> Robby Pelssers schrieb:
>
>> Hi all,
>>
>> we have cocoon2.1.10 running on a solaris(OS version5.8). The server
>> has 16G of memory and 2 processors (sparcv9 processors operating at
>> 900 MHz). Cocoon is running on tomcat/4.1.24.
>>
>> After a while we see our CPU increasing to about 94% and the system
>> becomes non-responsive. Could anybody point to what we look for? We
>> can't trace the problem back from the tomcat loggings.
>>
>> Cheers,
>> Robby Pelssers
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problem with tuning JVM (high CPU load)
Posted by Thomas Markus <t....@proventis.net>.
if your free memory is low, the jvm runs the gc automatically. in case
your free memory is very low the gc runs very often and consumes a lot
of cpu. try to log your current memory state in that situation.
Robby Pelssers schrieb:
> Hi Thomas,
>
> Actually, we scheduled the garbage collector as a cron job to run every
> day at night between 2 and 3 o'clock two times to make sure memory is
> freed up when daily operations start again around 7-8 o'clock. I don't
> really see how running the garbage collector can have a negative affect?
> And even if there is a memory leak, how do you explain the high CPU
> load?
>
> Cheers,
> Robby
>
> -----Oorspronkelijk bericht-----
> Van: Thomas Markus [mailto:t.markus@proventis.net]
> Verzonden: woensdag, mei 2007 9:26
> Aan: users@cocoon.apache.org
> Onderwerp: Re: Problem with tuning JVM (high CPU load)
>
> Hi,
>
> looks like a memory leak. maybe the garbage collector runs very often
>
> thomas
>
>
> Robby Pelssers schrieb:
>
>> Hi all,
>>
>> we have cocoon2.1.10 running on a solaris(OS version5.8). The server
>> has 16G of memory and 2 processors (sparcv9 processors operating at
>> 900 MHz). Cocoon is running on tomcat/4.1.24.
>>
>> After a while we see our CPU increasing to about 94% and the system
>> becomes non-responsive. Could anybody point to what we look for? We
>> can't trace the problem back from the tomcat loggings.
>>
>> Cheers,
>> Robby Pelssers
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
RE: Problem with tuning JVM (high CPU load)
Posted by Robby Pelssers <rp...@agp.nl>.
Hi Thomas,
Actually, we scheduled the garbage collector as a cron job to run every
day at night between 2 and 3 o'clock two times to make sure memory is
freed up when daily operations start again around 7-8 o'clock. I don't
really see how running the garbage collector can have a negative affect?
And even if there is a memory leak, how do you explain the high CPU
load?
Cheers,
Robby
-----Oorspronkelijk bericht-----
Van: Thomas Markus [mailto:t.markus@proventis.net]
Verzonden: woensdag, mei 2007 9:26
Aan: users@cocoon.apache.org
Onderwerp: Re: Problem with tuning JVM (high CPU load)
Hi,
looks like a memory leak. maybe the garbage collector runs very often
thomas
Robby Pelssers schrieb:
>
> Hi all,
>
> we have cocoon2.1.10 running on a solaris(OS version5.8). The server
> has 16G of memory and 2 processors (sparcv9 processors operating at
> 900 MHz). Cocoon is running on tomcat/4.1.24.
>
> After a while we see our CPU increasing to about 94% and the system
> becomes non-responsive. Could anybody point to what we look for? We
> can't trace the problem back from the tomcat loggings.
>
> Cheers,
> Robby Pelssers
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problem with tuning JVM (high CPU load)
Posted by Thomas Markus <t....@proventis.net>.
Hi,
looks like a memory leak. maybe the garbage collector runs very often
thomas
Robby Pelssers schrieb:
>
> Hi all,
>
> we have cocoon2.1.10 running on a solaris(OS version5.8). The server
> has 16G of memory and 2 processors (sparcv9 processors operating at
> 900 MHz). Cocoon is running on tomcat/4.1.24.
>
> After a while we see our CPU increasing to about 94% and the system
> becomes non-responsive. Could anybody point to what we look for? We
> can't trace the problem back from the tomcat loggings.
>
> Cheers,
> Robby Pelssers
>