[MRM-1457] Cpu usage 100%

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.3.2, 1.3.3, 1.3.4
• Fix Version/s: 1.3.5
• Component/s: Problem Reporting
• Environment: SLES 11, 4 GB Ram, 1 Core CPU
• Assignee: Maria Odea B. Ching
• Reporter: Benjamin Knoth
• Created: 22/Feb/11 02:25
• Updated: 06/May/11 02:41
• Resolved: 06/May/11 02:41

Description

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.

Issue Links

• duplicates: MRM-665 DependencyTree fetchGraph causes high load with large databases