You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Benjamin Knoth (JIRA)" <ji...@codehaus.org> on 2011/02/22 09:29:22 UTC

[jira] Updated: (MRM-1457) Cpu usage 100%

     [ http://jira.codehaus.org/browse/MRM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Knoth updated MRM-1457:
--------------------------------

    Attachment: jconsole-heap-memory.png

Now all complete.

> Cpu usage 100%
> --------------
>
>                 Key: MRM-1457
>                 URL: http://jira.codehaus.org/browse/MRM-1457
>             Project: Archiva
>          Issue Type: Bug
>          Components: Problem Reporting
>    Affects Versions: 1.3.2, 1.3.3, 1.3.4
>         Environment: SLES 11, 4 GB Ram, 1 Core CPU
>            Reporter: Benjamin Knoth
>            Priority: Critical
>         Attachments: jconsole-heap-memory.png, jconsole-stack-trace.png, jconsole-stack-trace1.png, jconsole-stack-track2.png, jconsole-top threads.png, jconsole-top-threads.png, overview-jconsole.png
>
>
> we use Archiva and we have problems with our cpu usage.
> If i restart archiva everything is running fine. After 3-6 hours the
> java process of archiva use 100% of the cpu from one to the next
> moment. We had this problem on Archiva 1.3.1 and 1.3.3. On Archiva
> 1.3.1 it came after the 3-5 times where the db artefacts were updated.
> The snapshot repository need 12 minutes. I deleted some snapshots.
> Lasst week we updated it to 1.3.3 and now i can't find something
> important on log. On the last 100% usage problem i got a message from
> nagios the usage of cpu is critcal at 7:43 o'clock, but in the log i
> found only this messages.
> At the moment archiva 1.3.4 is installed.
> > Am 21.02.2011 17:27, schrieb Brent Atkinson:
> > >> The screen with the red
> > >> bar at 99%, you need to select the thread and expand the bottom window. It
> > >> should show the stack trace which will give us the location in the code
> > >> where the cpu time is being consumed.
> > > Hi,
> > > i added 3 screenshots.
> > > Now 2 threads use many cpu.
> > > 
> > > Jconsole-stack-trace.png and Jconsole-stack-trace1.png is from btpool0-6
> > > and Jconsole-stack-trace2.png from btpool0-9.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira