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:27:22 UTC
[jira] Created: (MRM-1457) Cpu usage 100%
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.4, 1.3.3, 1.3.2
Environment: SLES 11, 4 GB Ram, 1 Core CPU
Reporter: Benjamin Knoth
Priority: Critical
Attachments: jconsole-stack-trace.png, jconsole-stack-trace1.png, jconsole-stack-track2.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
[jira] Commented: (MRM-1457) Cpu usage 100%
Posted by "Benjamin Knoth (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259440#action_259440 ]
Benjamin Knoth commented on MRM-1457:
-------------------------------------
It's possible.
> 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
[jira] Commented: (MRM-1457) Cpu usage 100%
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260461#action_260461 ]
Brett Porter commented on MRM-1457:
-----------------------------------
Sorry about the inconvenience. I'll disable this in an upcoming 1.3.5 release, and it will return in 1.4 without the performance issue.
> 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
[jira] Updated: (MRM-1457) Cpu usage 100%
Posted by "Benjamin Knoth (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Assigned: (MRM-1457) Cpu usage 100%
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching reassigned MRM-1457:
-------------------------------------
Assignee: Maria Odea Ching
> 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
> Assignee: Maria Odea Ching
> Priority: Critical
> Fix For: 1.3.5
>
> 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
[jira] Closed: (MRM-1457) Cpu usage 100%
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching closed MRM-1457.
---------------------------------
Resolution: Fixed
Dependency tree disabled in 1.3.x branch for now in [-r1100112|http://svn.apache.org/viewvc?rev=1100112&view=rev].
> 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
> Assignee: Maria Odea Ching
> Priority: Critical
> Fix For: 1.3.5
>
> 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
[jira] Updated: (MRM-1457) Cpu usage 100%
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1457:
------------------------------
Fix Version/s: 1.3.5
> 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
> Fix For: 1.3.5
>
> 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
[jira] Commented: (MRM-1457) Cpu usage 100%
Posted by "Benjamin Knoth (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260381#action_260381 ]
Benjamin Knoth commented on MRM-1457:
-------------------------------------
Since two weeks it run normal without 100% cpu usage.
> 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
[jira] Updated: (MRM-1457) Cpu usage 100%
Posted by "Benjamin Knoth (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Knoth updated MRM-1457:
--------------------------------
Attachment: jconsole-top threads.png
overview-jconsole.png
jconsole-top-threads.png
To complete the status of topthread plugin of jconsole.
> 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