You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Benjamin Knoth <kn...@mpdl.mpg.de> on 2011/02/08 09:13:50 UTC
100 %cpu usage
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
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.
2011-02-08 07:00:13,123 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Started: [snapshots]
/data/archiva/rep
ositories/snapshots
2011-02-08 07:00:15,778 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
processed artifacts
2011-02-08 07:00:18,778 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Finished: [snapshots]
/data/archiva/re
positories/snapshots
2011-02-08 07:00:18,778 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Finished
repository task:
.\ Scan of snapshots \.__________________________________________
Repository Dir : /data/archiva/repositories/snapshots
Repository Name : Archiva Managed Snapshot Repository
Repository Layout : default
Known Consumers : (1 configured)
update-db-artifact (Total: 2592ms; Avg.: 1296;
Count: 2)
Invalid Consumers : <none>
Duration : 5 Seconds 654 Milliseconds
When Gathered : 2/8/11 7:00 AM
Total File Count : 22879
Avg Time Per File :
______________________________________________________________
2011-02-08 07:00:49,254 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Finished database task
in 49230ms.
2011-02-08 08:00:00,022 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Executing task from
queue with job
name: DatabaseTask
2011-02-08 08:00:00,022 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
unprocessed artifac
ts
2011-02-08 08:00:00,046 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Executing task
from queue with
job name: RepositoryTask [repositoryId=internal, resourceFile=null,
scanAll=false
, updateRelatedArtifacts=false]
2011-02-08 08:00:00,119 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Started: [internal]
/data/archiva/repo
sitories/internal
2011-02-08 08:00:02,229 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
processed artifacts
2011-02-08 08:00:10,753 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Finished: [internal]
/data/archiva/rep
ositories/internal
2011-02-08 08:00:10,753 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Finished
repository task:
.\ Scan of internal \.__________________________________________
Repository Dir : /data/archiva/repositories/internal
Repository Name : Archiva Managed Internal Repository
Repository Layout : default
Known Consumers : (1 configured)
update-db-artifact
Invalid Consumers : <none>
Duration : 10 Seconds 634 Milliseconds
When Gathered : 2/8/11 8:00 AM
Total File Count : 55540
Avg Time Per File :
______________________________________________________________
What should i do to resolve this problem.
Best regards
Benjamin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJNUPs+AAoJEALVkoFaZmWjK/4QAKEU4TbPjTfmqbPbpUC5Wfxp
ivZ9epIlwX5DkMVj73weIdTC0Xs2JL/qx6smdM9EN0npe+LYSqOFle+1QAkJFc9t
w6XyUSy0YvIkNHKy0HmNxJyiII9/DXdnfnmawfYBrPB2XUbR1aRmqTsH9Wo7uy3K
NP2x1KaAGTZkMHpB8lBH2wVn4Z/eKjbU9+OX0XspmWp3ukheCC8GgJuv4zmbH22E
Yu3vjwOkKfCV7LkE0Gnq0BFrdn3J9xOEodOQWXB2au6UCpIQa1eYSh2oorRMoajR
5DEkTjYsy44YLLHIl8m7xUQMmVXyLx49dwsB1kdHXxpO5PKyI/jYFhc+nP1qRiAZ
h1zHQZvVklBrFRTWb4GfIE0IL9oUubWQlXHtq5QAR+C1uIJSdIvX1KePaRN2EA1k
lYh/wZ4kYlvcU/1UAhyfP79eDJgQcnyGrk9ZJeFWJ9+KkvJ5CFoajjlYlP3SECP3
Y0xSOneJo0VWWbKAv4EycJ9Amk2DjenUpmndU7qazXj+v/C7z6mKHxtz6VeOQu2X
8n0gi99VUQ3EcOBlrAI+ccv8/45vKNHNGiamoTnnNAbCwXDjJXBHU9mY2IxXYVPt
9R4Gd6WaJsk0tHLK4h3U9NgywJObzWcAUHqJEx2s+br3ptgidA843HP27FHvTJyG
8+Yjn5db9IrK1nkOHNWV
=IRy/
-----END PGP SIGNATURE-----
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
Update: we updated Archiva to 1.3.4. last Wednesday same problem.
Yesterday archiva used 100% of CPU since 14:06
14:02 1%
14:04 21%
14:06 100%
Am 16.02.2011 02:24, schrieb Brett Porter:
>
> On 16/02/2011, at 2:14 AM, Benjamin Knoth wrote:
>
>> Sorry only one java process is running.
>> But two processes from archiva.
>> If i start archiva dump i get this two messages.
>> Dumping Apache Archiva...
>> Dumped Apache Archiva.
>
> Ok, this is normal.
>
>>
>> But i can see any changes on archiva.pid or new processes of archiva or
>> dump.
>
> You should see in ./logs/wrapper.$DATE.log a large output of what all the threads are doing.
In wrapper.log is any log between 04:18 and 17:06
INFO | jvm 1 | 2011/02/17 04:18:17 | at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
STATUS | wrapper | 2011/02/17 17:06:06 | TERM trapped. Shutting down.
INFO | jvm 1 | 2011/02/17 17:06:07 | 2011-02-17 17:06:07.429::INFO:
Shutdown hook executing
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
No Log on archiva-audit.log, archiva.log in this time.
The last log was in archiva-security-audit.log
2011-02-17 13:45:01 - - Successful Login for user
In request.log if found this logs in this time
134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
/archiva/repository/internal HTTP/1.1" 302 0 "-" "Java/1.6.0_20"
134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
/archiva/repository/internal/ HTTP/1.1" 200 19332 "-" "Java/1.6.0_20"
134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
/archiva/repository/snapshots HTTP/1.1" 302 0 "-" "Java/1.6.0_20"
134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
/archiva/repository/snapshots/ HTTP/1.1" 200 370 "-" "Java/1.6.0_20"
134.76.28.224 - - [17/Feb/2011:14:02:29 +0000] "HEAD
/archiva/repository/internal//axis/axis/1.4/axis-1.4.jar HTTP/1.1" 200 0
"-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:34 +0000] "HEAD
/archiva/repository/internal//axis/axis-wsdl4j/1.5.1/axis-wsdl4j-1.5.1.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:39 +0000] "HEAD
/archiva/repository/internal//bcel/bcel/5.1/bcel-5.1.jar HTTP/1.1" 200 0
"-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:41 +0000] "GET /archiva/
HTTP/1.1" 302 0 "-" "OpenNMS HttpMonitor"
134.76.28.224 - - [17/Feb/2011:14:02:43 +0000] "HEAD
/archiva/repository/internal//bouncycastle/bcmail-jdk14/138/bcmail-jdk14-138.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:49 +0000] "HEAD
/archiva/repository/internal//bouncycastle/bcprov-jdk14/138/bcprov-jdk14-138.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:54 +0000] "HEAD
/archiva/repository/internal//com/lowagie/itext/2.1.5/itext-2.1.5.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:03:44 +0000] "HEAD
/archiva/repository/internal//com/maxmind/geoip/geoip/1.2.3/geoip-1.2.3.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.212 - - [17/Feb/2011:14:03:50 +0000] "GET / HTTP/1.1" 404
786 "-" "OpenNMS HttpMonitor"
134.76.28.224 - - [17/Feb/2011:14:03:49 +0000] "HEAD
/archiva/repository/internal//commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) mav
en-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:03:54 +0000] "HEAD
/archiva/repository/internal//commons-codec/commons-codec/1.3/commons-codec-1.3.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.
1"
134.76.28.224 - - [17/Feb/2011:14:03:59 +0000] "HEAD
/archiva/repository/internal//commons-collections/commons-collections/3.2/commons-collections-3.2.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) m
aven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:04 +0000] "HEAD
/archiva/repository/internal//commons-digester/commons-digester/1.8/commons-digester-1.8.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-arti
fact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:09 +0000] "HEAD
/archiva/repository/internal//commons-discovery/commons-discovery/0.2/commons-discovery-0.2.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-a
rtifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:14 +0000] "HEAD
/archiva/repository/internal//commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:22 +0000] "HEAD
/archiva/repository/internal//commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-art
ifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:27 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/citationmanager/1.0.60/citationmanager-1.0.60.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:33 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/common_logic/1.1.55/common_logic-1.1.55.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven
-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:38 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/common_logic/1.1.55/common_logic-1.1.55.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven
-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:43 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/dataacquisition/1.0.52/dataacquisition-1.0.52.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:47 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/framework_access/1.0.58/framework_access-1.0.58.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.6.35-25-generi
c) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:52 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/search/1.0.55/search-1.0.55.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.
2.1"
134.76.28.224 - - [17/Feb/2011:14:04:56 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/structuredexportmanager/1.0.58/structuredexportmanager-1.0.58.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.
6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:01 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/transformation/1.0.43/transformation-1.0.43.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) m
aven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:06 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/validation/1.0.62/validation-1.0.62.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-art
ifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:11 +0000] "HEAD
/archiva/repository/internal//dom4j/dom4j/1.6.1/dom4j-1.6.1.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:16 +0000] "HEAD
/archiva/repository/internal//eclipse/jdtcore/3.1.0/jdtcore-3.1.0.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:20 +0000] "HEAD
/archiva/repository/internal//external/java_assist/3.9.0/java_assist-3.9.0.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:25 +0000] "HEAD
/archiva/repository/internal//external/scannotation/1.0.2/scannotation-1.0.2.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:58 +0000] "GET /archiva/
HTTP/1.1" 302 0 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
Best regards
Benjamin
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
Ok, i created a new issues.
You can find it at http://jira.codehaus.org/browse/MRM-1457.
Best regards
Benjamin
Am 21.02.2011 23:04, schrieb Brett Porter:
> screenshots aren't sent to the mailing list - please open a jira ticket and attach them there.
>
> Thanks,
> Brett
>
> On 22/02/2011, at 4:10 AM, Benjamin Knoth wrote:
>
>> 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.
>>
>> Benjamin
>>
>>
>> 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.
>>
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
--
Benjamin Knoth
Max Planck Digital Library (MPDL)
Systemadministration
Amalienstrasse 33
80799 Munich, Germany
http://www.mpdl.mpg.de
Mail: knoth@mpdl.mpg.de
Phone: +49 89 38602 202
Fax: +49-89-38602-280
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
screenshots aren't sent to the mailing list - please open a jira ticket and attach them there.
Thanks,
Brett
On 22/02/2011, at 4:10 AM, Benjamin Knoth wrote:
> 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.
>
> Benjamin
>
>
> 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.
>
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
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.
Benjamin
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.
Re: 100 %cpu usage
Posted by Brent Atkinson <ba...@apache.org>.
Great,
The only thing missing from the screen shot is the stack trace that shows
where in the code the thread is spending its time. 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.
Brent
On Mon, Feb 21, 2011 at 10:31 AM, Benjamin Knoth <kn...@mpdl.mpg.de> wrote:
> Ok i added some screenshots as attachment.
> I hope it will help.
>
> Benjamin
>
> Am 18.02.2011 14:37, schrieb Brent Atkinson:
> > Sending along a screen shot showing the stack trace from
> > the offending thread(s) would help immensely since we can't see the
> > specifics of your environment.
>
>
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
Ok i added some screenshots as attachment.
I hope it will help.
Benjamin
Am 18.02.2011 14:37, schrieb Brent Atkinson:
> Sending along a screen shot showing the stack trace from
> the offending thread(s) would help immensely since we can't see the
> specifics of your environment.
Re: 100 %cpu usage
Posted by Brent Atkinson <br...@gmail.com>.
Hi,
There are multiple tools to do this, but Java 6 comes with jconsole and
there's a third party plugin called topthreads that allows you to see the
thread, class and method that is taking up time. It's not a full profiler,
but it's simple enough to get some decent information about where the issues
are.
The plugin: http://lsd.luminis.nl/top-threads-plugin-for-jconsole/
You just need to fire up jconsole with the plugin enabled when you're seeing
the 100% cpu usage. Sending along a screen shot showing the stack trace from
the offending thread(s) would help immensely since we can't see the
specifics of your environment.
Brent
On Fri, Feb 18, 2011 at 3:06 AM, Benjamin Knoth <kn...@mpdl.mpg.de> wrote:
> Yesterday archiva used 100% of CPU since 14:06
>
> 14:02 1%
> 14:04 21%
> 14:06 100%
>
> Am 16.02.2011 02:24, schrieb Brett Porter:
> >
> > On 16/02/2011, at 2:14 AM, Benjamin Knoth wrote:
> >
> >> Sorry only one java process is running.
> >> But two processes from archiva.
> >> If i start archiva dump i get this two messages.
> >> Dumping Apache Archiva...
> >> Dumped Apache Archiva.
> >
> > Ok, this is normal.
> >
> >>
> >> But i can see any changes on archiva.pid or new processes of archiva or
> >> dump.
> >
> > You should see in ./logs/wrapper.$DATE.log a large output of what all the
> threads are doing.
>
> In wrapper.log is any log between 04:18 and 17:06
>
> INFO | jvm 1 | 2011/02/17 04:18:17 | at
>
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
> STATUS | wrapper | 2011/02/17 17:06:06 | TERM trapped. Shutting down.
> INFO | jvm 1 | 2011/02/17 17:06:07 | 2011-02-17 17:06:07.429::INFO:
> Shutdown hook executing
>
>
> >
> > - Brett
> >
> > --
> > Brett Porter
> > brett@apache.org
> > http://brettporter.wordpress.com/
> > http://au.linkedin.com/in/brettporter
> >
> >
> >
> >
>
> No Log on archiva-audit.log, archiva.log in this time.
>
>
> The last log was in archiva-security-audit.log
> 2011-02-17 13:45:01 - - Successful Login for user
>
>
>
> In request.log if found this logs in this time
>
> 134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
> /archiva/repository/internal HTTP/1.1" 302 0 "-" "Java/1.6.0_20"
> 134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
> /archiva/repository/internal/ HTTP/1.1" 200 19332 "-" "Java/1.6.0_20"
> 134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
> /archiva/repository/snapshots HTTP/1.1" 302 0 "-" "Java/1.6.0_20"
> 134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
> /archiva/repository/snapshots/ HTTP/1.1" 200 370 "-" "Java/1.6.0_20"
> 134.76.28.224 - - [17/Feb/2011:14:02:29 +0000] "HEAD
> /archiva/repository/internal//axis/axis/1.4/axis-1.4.jar HTTP/1.1" 200 0
> "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.6.35-25-generic)
> maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:02:34 +0000] "HEAD
> /archiva/repository/internal//axis/axis-wsdl4j/1.5.1/axis-wsdl4j-1.5.1.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:02:39 +0000] "HEAD
> /archiva/repository/internal//bcel/bcel/5.1/bcel-5.1.jar HTTP/1.1" 200 0
> "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.6.35-25-generic)
> maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:02:41 +0000] "GET /archiva/
> HTTP/1.1" 302 0 "-" "OpenNMS HttpMonitor"
> 134.76.28.224 - - [17/Feb/2011:14:02:43 +0000] "HEAD
>
> /archiva/repository/internal//bouncycastle/bcmail-jdk14/138/bcmail-jdk14-138.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:02:49 +0000] "HEAD
>
> /archiva/repository/internal//bouncycastle/bcprov-jdk14/138/bcprov-jdk14-138.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:02:54 +0000] "HEAD
> /archiva/repository/internal//com/lowagie/itext/2.1.5/itext-2.1.5.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:03:44 +0000] "HEAD
> /archiva/repository/internal//com/maxmind/geoip/geoip/1.2.3/geoip-1.2.3.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.212 - - [17/Feb/2011:14:03:50 +0000] "GET / HTTP/1.1" 404
> 786 "-" "OpenNMS HttpMonitor"
> 134.76.28.224 - - [17/Feb/2011:14:03:49 +0000] "HEAD
>
> /archiva/repository/internal//commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) mav
> en-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:03:54 +0000] "HEAD
>
> /archiva/repository/internal//commons-codec/commons-codec/1.3/commons-codec-1.3.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.
> 1"
> 134.76.28.224 - - [17/Feb/2011:14:03:59 +0000] "HEAD
>
> /archiva/repository/internal//commons-collections/commons-collections/3.2/commons-collections-3.2.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) m
> aven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:04 +0000] "HEAD
>
> /archiva/repository/internal//commons-digester/commons-digester/1.8/commons-digester-1.8.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-arti
> fact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:09 +0000] "HEAD
>
> /archiva/repository/internal//commons-discovery/commons-discovery/0.2/commons-discovery-0.2.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-a
> rtifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:14 +0000] "HEAD
>
> /archiva/repository/internal//commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic)
> maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:22 +0000] "HEAD
>
> /archiva/repository/internal//commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-art
> ifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:27 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/citationmanager/1.0.60/citationmanager-1.0.60.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic)
> maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:33 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/common_logic/1.1.55/common_logic-1.1.55.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven
> -artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:38 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/common_logic/1.1.55/common_logic-1.1.55.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven
> -artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:43 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/dataacquisition/1.0.52/dataacquisition-1.0.52.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic)
> maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:47 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/framework_access/1.0.58/framework_access-1.0.58.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generi
> c) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:52 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/search/1.0.55/search-1.0.55.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.
> 2.1"
> 134.76.28.224 - - [17/Feb/2011:14:04:56 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/structuredexportmanager/1.0.58/structuredexportmanager-1.0.58.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.
> 6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:05:01 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/transformation/1.0.43/transformation-1.0.43.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) m
> aven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:05:06 +0000] "HEAD
>
> /archiva/repository/internal//de/mpg/escidoc/services/validation/1.0.62/validation-1.0.62.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-art
> ifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:05:11 +0000] "HEAD
> /archiva/repository/internal//dom4j/dom4j/1.6.1/dom4j-1.6.1.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:05:16 +0000] "HEAD
> /archiva/repository/internal//eclipse/jdtcore/3.1.0/jdtcore-3.1.0.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:05:20 +0000] "HEAD
>
> /archiva/repository/internal//external/java_assist/3.9.0/java_assist-3.9.0.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:05:25 +0000] "HEAD
>
> /archiva/repository/internal//external/scannotation/1.0.2/scannotation-1.0.2.jar
> HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
> 2.6.35-25-generic) maven-artifact/2.2.1"
> 134.76.28.224 - - [17/Feb/2011:14:05:58 +0000] "GET /archiva/
> HTTP/1.1" 302 0 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
>
>
> Best regards
>
> Benjamin
>
>
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
Yesterday archiva used 100% of CPU since 14:06
14:02 1%
14:04 21%
14:06 100%
Am 16.02.2011 02:24, schrieb Brett Porter:
>
> On 16/02/2011, at 2:14 AM, Benjamin Knoth wrote:
>
>> Sorry only one java process is running.
>> But two processes from archiva.
>> If i start archiva dump i get this two messages.
>> Dumping Apache Archiva...
>> Dumped Apache Archiva.
>
> Ok, this is normal.
>
>>
>> But i can see any changes on archiva.pid or new processes of archiva or
>> dump.
>
> You should see in ./logs/wrapper.$DATE.log a large output of what all the threads are doing.
In wrapper.log is any log between 04:18 and 17:06
INFO | jvm 1 | 2011/02/17 04:18:17 | at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
STATUS | wrapper | 2011/02/17 17:06:06 | TERM trapped. Shutting down.
INFO | jvm 1 | 2011/02/17 17:06:07 | 2011-02-17 17:06:07.429::INFO:
Shutdown hook executing
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
No Log on archiva-audit.log, archiva.log in this time.
The last log was in archiva-security-audit.log
2011-02-17 13:45:01 - - Successful Login for user
In request.log if found this logs in this time
134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
/archiva/repository/internal HTTP/1.1" 302 0 "-" "Java/1.6.0_20"
134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
/archiva/repository/internal/ HTTP/1.1" 200 19332 "-" "Java/1.6.0_20"
134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
/archiva/repository/snapshots HTTP/1.1" 302 0 "-" "Java/1.6.0_20"
134.76.28.224 - - [17/Feb/2011:14:02:25 +0000] "GET
/archiva/repository/snapshots/ HTTP/1.1" 200 370 "-" "Java/1.6.0_20"
134.76.28.224 - - [17/Feb/2011:14:02:29 +0000] "HEAD
/archiva/repository/internal//axis/axis/1.4/axis-1.4.jar HTTP/1.1" 200 0
"-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:34 +0000] "HEAD
/archiva/repository/internal//axis/axis-wsdl4j/1.5.1/axis-wsdl4j-1.5.1.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:39 +0000] "HEAD
/archiva/repository/internal//bcel/bcel/5.1/bcel-5.1.jar HTTP/1.1" 200 0
"-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:41 +0000] "GET /archiva/
HTTP/1.1" 302 0 "-" "OpenNMS HttpMonitor"
134.76.28.224 - - [17/Feb/2011:14:02:43 +0000] "HEAD
/archiva/repository/internal//bouncycastle/bcmail-jdk14/138/bcmail-jdk14-138.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:49 +0000] "HEAD
/archiva/repository/internal//bouncycastle/bcprov-jdk14/138/bcprov-jdk14-138.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:02:54 +0000] "HEAD
/archiva/repository/internal//com/lowagie/itext/2.1.5/itext-2.1.5.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:03:44 +0000] "HEAD
/archiva/repository/internal//com/maxmind/geoip/geoip/1.2.3/geoip-1.2.3.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.212 - - [17/Feb/2011:14:03:50 +0000] "GET / HTTP/1.1" 404
786 "-" "OpenNMS HttpMonitor"
134.76.28.224 - - [17/Feb/2011:14:03:49 +0000] "HEAD
/archiva/repository/internal//commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) mav
en-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:03:54 +0000] "HEAD
/archiva/repository/internal//commons-codec/commons-codec/1.3/commons-codec-1.3.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.
1"
134.76.28.224 - - [17/Feb/2011:14:03:59 +0000] "HEAD
/archiva/repository/internal//commons-collections/commons-collections/3.2/commons-collections-3.2.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) m
aven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:04 +0000] "HEAD
/archiva/repository/internal//commons-digester/commons-digester/1.8/commons-digester-1.8.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-arti
fact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:09 +0000] "HEAD
/archiva/repository/internal//commons-discovery/commons-discovery/0.2/commons-discovery-0.2.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-a
rtifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:14 +0000] "HEAD
/archiva/repository/internal//commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:22 +0000] "HEAD
/archiva/repository/internal//commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-art
ifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:27 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/citationmanager/1.0.60/citationmanager-1.0.60.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:33 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/common_logic/1.1.55/common_logic-1.1.55.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven
-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:38 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/common_logic/1.1.55/common_logic-1.1.55.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven
-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:43 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/dataacquisition/1.0.52/dataacquisition-1.0.52.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic)
maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:47 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/framework_access/1.0.58/framework_access-1.0.58.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.6.35-25-generi
c) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:04:52 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/search/1.0.55/search-1.0.55.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.
2.1"
134.76.28.224 - - [17/Feb/2011:14:04:56 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/structuredexportmanager/1.0.58/structuredexportmanager-1.0.58.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux 2.
6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:01 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/transformation/1.0.43/transformation-1.0.43.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) m
aven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:06 +0000] "HEAD
/archiva/repository/internal//de/mpg/escidoc/services/validation/1.0.62/validation-1.0.62.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-art
ifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:11 +0000] "HEAD
/archiva/repository/internal//dom4j/dom4j/1.6.1/dom4j-1.6.1.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:16 +0000] "HEAD
/archiva/repository/internal//eclipse/jdtcore/3.1.0/jdtcore-3.1.0.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:20 +0000] "HEAD
/archiva/repository/internal//external/java_assist/3.9.0/java_assist-3.9.0.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:25 +0000] "HEAD
/archiva/repository/internal//external/scannotation/1.0.2/scannotation-1.0.2.jar
HTTP/1.1" 200 0 "-" "Apache-Maven/2.2 (Java 1.6.0_20; Linux
2.6.35-25-generic) maven-artifact/2.2.1"
134.76.28.224 - - [17/Feb/2011:14:05:58 +0000] "GET /archiva/
HTTP/1.1" 302 0 "-" "check_http/v1.4.15 (nagios-plugins 1.4.15)"
Best regards
Benjamin
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
On 16/02/2011, at 2:14 AM, Benjamin Knoth wrote:
> Sorry only one java process is running.
> But two processes from archiva.
> If i start archiva dump i get this two messages.
> Dumping Apache Archiva...
> Dumped Apache Archiva.
Ok, this is normal.
>
> But i can see any changes on archiva.pid or new processes of archiva or
> dump.
You should see in ./logs/wrapper.$DATE.log a large output of what all the threads are doing.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
Am 15.02.2011 06:42, schrieb Brett Porter:
>
> On 14/02/2011, at 10:09 PM, Benjamin Knoth wrote:
>
>> If i use archiva dump on 100 cpu usage it creates a dump of the java
>> process with a high pid. This process runs normally with 0 % cpu and 4.9
>> % Mem. But if i restart archiva and make a dump with archiva dump i
>> didn't found a second java process on top.
>
> This sounds a little weird. You have two java processes running? Or only when the dump is done? (haven't noticed that before - but the dump runs too fast to check).
Sorry only one java process is running.
But two processes from archiva.
If i start archiva dump i get this two messages.
Dumping Apache Archiva...
Dumped Apache Archiva.
But i can see any changes on archiva.pid or new processes of archiva or
dump.
This Processes did i found with ps aux | grep archiva
root 21392 0.0 0.0 10000 620 ? Sl 12:36 0:00
/data/archiva/apache-archiva-1.3.3/bin/./wrapper-linux-x86-32
/data/archiva/apache-archiva-1.3.3/bin/../conf/wrapper.conf
wrapper.syslog.ident=archiva
wrapper.pidfile=/data/archiva/apache-archiva-1.3.3/bin/../logs/archiva.pid
wrapper.daemonize=TRUE wrapper.lockfile=/var/lock/subsys/archiva
root 21394 99.9 9.4 876032 397936 ? Sl 12:36 169:52 java
-Dappserver.home=. -Dappserver.base=. -Djetty.logs=./logs -Xms512m
-Xmx512m -Djava.library.path=lib -classpath
lib/wrapper.jar:lib/archiva-jetty-1.3.3.pom:lib/jetty-6.1.19.jar:lib/jetty-util-6.1.19.jar:lib/servlet-api-2.5-20081211.jar:lib/start-6.1.19.jar:lib/jetty-naming-6.1.19.jar:lib/mail-1.4.jar:lib/jsp-2.1-jetty-6.1.19.jar:lib/core-3.1.1.jar:lib/jsp-api-2.1-glassfish-9.1.1.B60.25.p0.jar:lib/jsp-2.1-glassfish-9.1.1.B60.25.p0.jar:lib/ant-1.6.5.jar:lib/jetty-plus-6.1.19.jar:lib/geronimo-spec-jta-1.0.1B-rc4.jar:lib/derby-10.1.3.1.jar:lib/activation-1.1.jar:lib/commons-dbcp-1.2.1.jar:lib/commons-collections-3.2.jar:lib/commons-pool-1.2.jar:lib/xml-apis-1.0.b2.jar:lib/postgresql-9.0-801.jdbc3.jar
-Dwrapper.key=zXRSxqH5Ghp21yZj -Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
-Dwrapper.pid=21392 -Dwrapper.version=3.2.3
-Dwrapper.native_library=wrapper -Dwrapper.service=TRUE
-Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1
org.tanukisoftware.wrapper.WrapperSimpleApp org.mortbay.start.Main
./conf/jetty.xml
>
> You can confirm what is expected by checking the PID in ./logs/archiva.pid. Is that the one on 100% CPU?
No in archiva.pid is saved this pid 21392.
>
>> What should i do with the dump of archiva?
>
> Does the list of threads give any hint about what is going on in the server at that time? Perhaps you could attach that text to a jira issue for further investigation. We'd mainly be interested in anything that contains a trace from "org.apache.*"
>
>>
>> At the same time in meantime there are using max. 5 people archiva at
>> the same time.
>
> Given what you've shown in the logs, status page, and number of users so far, there should be no reason for the CPU to go to 100% at all, other than at pre-defined scanning intervals.
>
> I think we'll need to gather more logs or data via JIRA to figure out what's happening...
Ok
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
On 14/02/2011, at 10:09 PM, Benjamin Knoth wrote:
> If i use archiva dump on 100 cpu usage it creates a dump of the java
> process with a high pid. This process runs normally with 0 % cpu and 4.9
> % Mem. But if i restart archiva and make a dump with archiva dump i
> didn't found a second java process on top.
This sounds a little weird. You have two java processes running? Or only when the dump is done? (haven't noticed that before - but the dump runs too fast to check).
You can confirm what is expected by checking the PID in ./logs/archiva.pid. Is that the one on 100% CPU?
> What should i do with the dump of archiva?
Does the list of threads give any hint about what is going on in the server at that time? Perhaps you could attach that text to a jira issue for further investigation. We'd mainly be interested in anything that contains a trace from "org.apache.*"
>
> At the same time in meantime there are using max. 5 people archiva at
> the same time.
Given what you've shown in the logs, status page, and number of users so far, there should be no reason for the CPU to go to 100% at all, other than at pre-defined scanning intervals.
I think we'll need to gather more logs or data via JIRA to figure out what's happening...
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
Hi,
That's the request log from 11. februrary in this time where i got the
problem. There are only some monitoring requests from nagios and opennms.
I run it on Jetty standalone.
134.76.28.224 - - [11/Feb/2011:11:53:45 +0000] "GET /archiva/
HTTP/1.1" 302 0 "-" "check_http/v1.4.15 (nagi
os-plugins 1.4.15)"
134.76.28.224 - - [11/Feb/2011:11:56:06 +0000] "GET /archiva/
HTTP/1.1" 302 0 "-" "-"
134.76.28.212 - - [11/Feb/2011:11:56:06 +0000] "GET / HTTP/1.0" 404
786 "-" "-"
null - - [11/Feb/2011:11:56:18 +0000] "GET /opennms/index.jsp
HTTP/1.0" 404 1285 "-" "-"
null - - [11/Feb/2011:11:56:18 +0000] "GET /opennms/index.jsp
HTTP/1.0" 404 1285 "-" "-"
null - - [11/Feb/2011:11:56:18 +0000] "GET /opennms/index.jsp
HTTP/1.0" 404 1285 "-" "-"
134.76.28.212 - - [11/Feb/2011:11:57:37 +0000] "GET / HTTP/1.1" 404
786 "-" "OpenNMS HttpMonitor"
134.76.28.224 - - [11/Feb/2011:11:57:46 +0000] "GET /archiva/
HTTP/1.1" 302 0 "-" "OpenNMS HttpMonitor"
134.76.28.224 - - [11/Feb/2011:11:58:45 +0000] "GET /archiva/
HTTP/1.1" 302 0 "-" "check_http/v1.4.15 (nagi
os-plugins 1.4.15)"
If i use archiva dump on 100 cpu usage it creates a dump of the java
process with a high pid. This process runs normally with 0 % cpu and 4.9
% Mem. But if i restart archiva and make a dump with archiva dump i
didn't found a second java process on top.
What should i do with the dump of archiva?
At the same time in meantime there are using max. 5 people archiva at
the same time.
Best regards
Benjamin
Am 12.02.2011 02:05, schrieb Brett Porter:
>
> On 12/02/2011, at 12:37 AM, Benjamin Knoth wrote:
>
>> Hi,
>>
>> I restarted on 11:06.
>>
>> On 11:56 i got this messages.
>>
>> 2011-02-11 11:56:05,101 [btpool0-6] INFO
>> org.codehaus.plexus.redback.struts2.in
>> terceptor.ForceAdminUserInterceptor - Admin user found. No need to
>> configure ad
>> min user.
>> 2011-02-11 11:56:05,112 [btpool0-6] INFO
>> com.opensymphony.xwork2.validator.Acti
>> onValidatorManagerFactory - Detected AnnotationActionValidatorManager,
>> initiali
>> zing it...
>>
>>
>> On 11:55:52 archiva runs fine
>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>> 6765 root 16 0 798m 326m 11m S 0.0 8.0 0:28.37 java
>>
>> On 11:58:52 it runs with full cpu usage
>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>>
>> 6765 root 16 0 800m 346m 11m S 91.5 8.5 3:13.04 java
>>
>> After 12:01:52 it runs with 100% cpu usage. After restart it's all fine.
>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>>
>> 6765 root 16 0 800m 353m 11m S 99.5 8.6 6:12.21 java
>
> Very unusual. Can you confirm how many users are using it? How many requests are in the request log in a 1 minute period around these times?
>
> Also, can you try to get the thread dump as I indicated earlier? Are you using the Jetty standalone, or running in Tomcat, etc.? (in which case, try kill -3 $PID instead)
>
> Thanks,
> Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
--
Benjamin Knoth
Max Planck Digital Library (MPDL)
Systemadministration
Amalienstrasse 33
80799 Munich, Germany
http://www.mpdl.mpg.de
Mail: knoth@mpdl.mpg.de
Phone: +49 89 38602 202
Fax: +49-89-38602-280
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
On 12/02/2011, at 12:37 AM, Benjamin Knoth wrote:
> Hi,
>
> I restarted on 11:06.
>
> On 11:56 i got this messages.
>
> 2011-02-11 11:56:05,101 [btpool0-6] INFO
> org.codehaus.plexus.redback.struts2.in
> terceptor.ForceAdminUserInterceptor - Admin user found. No need to
> configure ad
> min user.
> 2011-02-11 11:56:05,112 [btpool0-6] INFO
> com.opensymphony.xwork2.validator.Acti
> onValidatorManagerFactory - Detected AnnotationActionValidatorManager,
> initiali
> zing it...
>
>
> On 11:55:52 archiva runs fine
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 6765 root 16 0 798m 326m 11m S 0.0 8.0 0:28.37 java
>
> On 11:58:52 it runs with full cpu usage
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
> 6765 root 16 0 800m 346m 11m S 91.5 8.5 3:13.04 java
>
> After 12:01:52 it runs with 100% cpu usage. After restart it's all fine.
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
> 6765 root 16 0 800m 353m 11m S 99.5 8.6 6:12.21 java
Very unusual. Can you confirm how many users are using it? How many requests are in the request log in a 1 minute period around these times?
Also, can you try to get the thread dump as I indicated earlier? Are you using the Jetty standalone, or running in Tomcat, etc.? (in which case, try kill -3 $PID instead)
Thanks,
Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
On 12/02/2011, at 1:15 AM, Chris Mylonas wrote:
> Hi Benjamin/Brett + Users,
>
> I've only been skimming this thread but am moving stuff across to archiva.
> i'm in a position to test on my setup something similar to what your doing
> to see if i get the same happening.
>
> all i've read so far is db-artifacts and something scanning once a day.
>
> if i wanted to replicate the setup somewhat, what should i be looking at
> doing - i'm pretty green/new with archiva (got a snapshot repository with a
> few artifacts)
>
> if i can set up scheduled tasks to replicate whatever's going on, let me
> know,
Based on the stats page shown earlier, there aren't any scheduled tasks running - maybe the thread dump will clear that up. The crons are set to the hour, so it shouldn't fire up at 11:58
I'm not sure how to go about replicating this behaviour.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Chris Mylonas <ch...@opencsta.org>.
Hi Benjamin/Brett + Users,
I've only been skimming this thread but am moving stuff across to archiva.
i'm in a position to test on my setup something similar to what your doing
to see if i get the same happening.
all i've read so far is db-artifacts and something scanning once a day.
if i wanted to replicate the setup somewhat, what should i be looking at
doing - i'm pretty green/new with archiva (got a snapshot repository with a
few artifacts)
if i can set up scheduled tasks to replicate whatever's going on, let me
know,
Cheers
Chris
On Sat, Feb 12, 2011 at 12:37 AM, Benjamin Knoth <kn...@mpdl.mpg.de> wrote:
> Hi,
>
> I restarted on 11:06.
>
> On 11:56 i got this messages.
>
> 2011-02-11 11:56:05,101 [btpool0-6] INFO
> org.codehaus.plexus.redback.struts2.in
> terceptor.ForceAdminUserInterceptor - Admin user found. No need to
> configure ad
> min user.
> 2011-02-11 11:56:05,112 [btpool0-6] INFO
> com.opensymphony.xwork2.validator.Acti
> onValidatorManagerFactory - Detected AnnotationActionValidatorManager,
> initiali
> zing it...
>
>
> On 11:55:52 archiva runs fine
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 6765 root 16 0 798m 326m 11m S 0.0 8.0 0:28.37 java
>
> On 11:58:52 it runs with full cpu usage
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
> 6765 root 16 0 800m 346m 11m S 91.5 8.5 3:13.04 java
>
> After 12:01:52 it runs with 100% cpu usage. After restart it's all fine.
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
> 6765 root 16 0 800m 353m 11m S 99.5 8.6 6:12.21 java
>
> Best regards
> Benjamin
>
>
> Am 11.02.2011 11:32, schrieb Benjamin Knoth:
> > I set the crons in achiva to check only 1 times a day in the night
> > (0:15, 1:15 and 2:15). I monitored it with snapshots of top.
> >
> > At 05:03:49 i got this:
> > 17453 root 18 0 873m 725m 11m S 1.9 17.7 28:37.38 java
> >
> > At 05:06:49 i got this:
> > 17453 root 18 0 873m 725m 11m S 52.2 17.7 30:11.36 java
> >
> > At 05:09:49 i got this:
> > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> >
> > 17453 root 18 0 873m 725m 11m S 99.8 17.7 33:11.01 java
> >
> > On 5 o'clock there wasn't run a cronjob.
> >
> > Today same problem a lot of faster.
> >
> > Restart at 08:47:34
> >
> > At 09:49:52
> >
> > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> >
> > 5504 root 15 0 856m 353m 11m S 99.8 8.6 3:19.09 java
> >
> > We haven't any prpblems with swap.
> > Swap: 4194296k total, 68k used, 4194228k free;
> >
> > What is maestro and what does it do. I can't find it in the standard
> > repository of sles..
> >
> > What should i do with the YourKit Java Profiler.
> > I haven't use this before.
> >
> > Benjamin
> >
> >
> > Am 09.02.2011 06:36, schrieb Brett Porter:
> >>
> >> On 08/02/2011, at 11:57 PM, Benjamin Knoth wrote:
> >>
> >>> Am 08.02.2011 12:38, schrieb Brett Porter:
> >>>>
> >>>> On 08/02/2011, at 8:00 PM, Benjamin Knoth wrote:
> >>>>
> >>>>> Hi Brett,
> >>>>> this is the output.
> >>>>
> >>>> Everything looks normal here - you're not running out of memory, and
> the scans are quick.
> >>>>
> >>>> You said the peaks coincided with the database scan in 1.3.1 - is that
> also the case in 1.3.3? Do they still last 12 minutes?
> >>>
> >>> No the last output in the log file which i send you was repeated 4
> times
> >>> with a difference of +- 2 seconds. But since 5 hours it runs with 100%
> >>> cpu usage.
> >>
> >> Sorry, I'd like to clarify I'm understanding correctly. What I've seen
> is the hourly scans completing in ~1-2 minutes (10 seconds for the
> repository scan, 50 seconds for the database scan). The status panel you
> showed had nothing queued. However, you're still seeing continuous 100%
> usage of the application for over 5 hours?
> >>
> >> How many requests is the box receiving? It doesn't appear you've got any
> problematic background processing, so it might be request load.
> >>
> >> Or is it possible that something else on the VM is constraining the
> resources it has? Or perhaps forcing swap space to be used?
> >>
> >>>
> >>> It's possible that i need 2 cores of cpu or should i change the memory
> >>> usage in archiva more than 1 GB ram. This VM have 4 GB Ram and 1 Core
> of
> >>> the CPU.
> >>
> >> 1 core should be fine. The status page showed only 144M of the RAM had
> been allocated (and only 48M used) out of the 991M you set aside, so that's
> not the issue.
> >>
> >> The only other investigation I can think of is to do a thread dump
> (./bin/maestro dump). If you are wanting to analyze it closely you could
> connect a profiler (like yourkit) to the running instance as well.
> >>
> >> - Brett
> >>
> >> --
> >> Brett Porter
> >> brett@apache.org
> >> http://brettporter.wordpress.com/
> >> http://au.linkedin.com/in/brettporter
> >>
> >>
> >>
> >>
> >
>
> --
> Benjamin Knoth
> Max Planck Digital Library (MPDL)
> Systemadministration
> Amalienstrasse 33
> 80799 Munich, Germany
> http://www.mpdl.mpg.de
>
> Mail: knoth@mpdl.mpg.de
> Phone: +49 89 38602 202
> Fax: +49-89-38602-280
>
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
Hi,
I restarted on 11:06.
On 11:56 i got this messages.
2011-02-11 11:56:05,101 [btpool0-6] INFO
org.codehaus.plexus.redback.struts2.in
terceptor.ForceAdminUserInterceptor - Admin user found. No need to
configure ad
min user.
2011-02-11 11:56:05,112 [btpool0-6] INFO
com.opensymphony.xwork2.validator.Acti
onValidatorManagerFactory - Detected AnnotationActionValidatorManager,
initiali
zing it...
On 11:55:52 archiva runs fine
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6765 root 16 0 798m 326m 11m S 0.0 8.0 0:28.37 java
On 11:58:52 it runs with full cpu usage
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6765 root 16 0 800m 346m 11m S 91.5 8.5 3:13.04 java
After 12:01:52 it runs with 100% cpu usage. After restart it's all fine.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6765 root 16 0 800m 353m 11m S 99.5 8.6 6:12.21 java
Best regards
Benjamin
Am 11.02.2011 11:32, schrieb Benjamin Knoth:
> I set the crons in achiva to check only 1 times a day in the night
> (0:15, 1:15 and 2:15). I monitored it with snapshots of top.
>
> At 05:03:49 i got this:
> 17453 root 18 0 873m 725m 11m S 1.9 17.7 28:37.38 java
>
> At 05:06:49 i got this:
> 17453 root 18 0 873m 725m 11m S 52.2 17.7 30:11.36 java
>
> At 05:09:49 i got this:
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
> 17453 root 18 0 873m 725m 11m S 99.8 17.7 33:11.01 java
>
> On 5 o'clock there wasn't run a cronjob.
>
> Today same problem a lot of faster.
>
> Restart at 08:47:34
>
> At 09:49:52
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
> 5504 root 15 0 856m 353m 11m S 99.8 8.6 3:19.09 java
>
> We haven't any prpblems with swap.
> Swap: 4194296k total, 68k used, 4194228k free;
>
> What is maestro and what does it do. I can't find it in the standard
> repository of sles..
>
> What should i do with the YourKit Java Profiler.
> I haven't use this before.
>
> Benjamin
>
>
> Am 09.02.2011 06:36, schrieb Brett Porter:
>>
>> On 08/02/2011, at 11:57 PM, Benjamin Knoth wrote:
>>
>>> Am 08.02.2011 12:38, schrieb Brett Porter:
>>>>
>>>> On 08/02/2011, at 8:00 PM, Benjamin Knoth wrote:
>>>>
>>>>> Hi Brett,
>>>>> this is the output.
>>>>
>>>> Everything looks normal here - you're not running out of memory, and the scans are quick.
>>>>
>>>> You said the peaks coincided with the database scan in 1.3.1 - is that also the case in 1.3.3? Do they still last 12 minutes?
>>>
>>> No the last output in the log file which i send you was repeated 4 times
>>> with a difference of +- 2 seconds. But since 5 hours it runs with 100%
>>> cpu usage.
>>
>> Sorry, I'd like to clarify I'm understanding correctly. What I've seen is the hourly scans completing in ~1-2 minutes (10 seconds for the repository scan, 50 seconds for the database scan). The status panel you showed had nothing queued. However, you're still seeing continuous 100% usage of the application for over 5 hours?
>>
>> How many requests is the box receiving? It doesn't appear you've got any problematic background processing, so it might be request load.
>>
>> Or is it possible that something else on the VM is constraining the resources it has? Or perhaps forcing swap space to be used?
>>
>>>
>>> It's possible that i need 2 cores of cpu or should i change the memory
>>> usage in archiva more than 1 GB ram. This VM have 4 GB Ram and 1 Core of
>>> the CPU.
>>
>> 1 core should be fine. The status page showed only 144M of the RAM had been allocated (and only 48M used) out of the 991M you set aside, so that's not the issue.
>>
>> The only other investigation I can think of is to do a thread dump (./bin/maestro dump). If you are wanting to analyze it closely you could connect a profiler (like yourkit) to the running instance as well.
>>
>> - Brett
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>> http://au.linkedin.com/in/brettporter
>>
>>
>>
>>
>
--
Benjamin Knoth
Max Planck Digital Library (MPDL)
Systemadministration
Amalienstrasse 33
80799 Munich, Germany
http://www.mpdl.mpg.de
Mail: knoth@mpdl.mpg.de
Phone: +49 89 38602 202
Fax: +49-89-38602-280
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
Sorry read mail back to front.
On 11/02/2011, at 9:32 PM, Benjamin Knoth wrote:
> What is maestro and what does it do. I can't find it in the standard
> repository of sles..
I meant ./bin/archiva dump (I typed our product name that uses the same commands on autopilot). That's if you use the standalone distribution, otherwise you need to kill -3 the pID
>
> What should i do with the YourKit Java Profiler.
> I haven't use this before.
That's only if you want to start debugging it yourself - it traces where in the code the CPU & memory is being used.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
I set the crons in achiva to check only 1 times a day in the night
(0:15, 1:15 and 2:15). I monitored it with snapshots of top.
At 05:03:49 i got this:
17453 root 18 0 873m 725m 11m S 1.9 17.7 28:37.38 java
At 05:06:49 i got this:
17453 root 18 0 873m 725m 11m S 52.2 17.7 30:11.36 java
At 05:09:49 i got this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
17453 root 18 0 873m 725m 11m S 99.8 17.7 33:11.01 java
On 5 o'clock there wasn't run a cronjob.
Today same problem a lot of faster.
Restart at 08:47:34
At 09:49:52
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5504 root 15 0 856m 353m 11m S 99.8 8.6 3:19.09 java
We haven't any prpblems with swap.
Swap: 4194296k total, 68k used, 4194228k free;
What is maestro and what does it do. I can't find it in the standard
repository of sles..
What should i do with the YourKit Java Profiler.
I haven't use this before.
Benjamin
Am 09.02.2011 06:36, schrieb Brett Porter:
>
> On 08/02/2011, at 11:57 PM, Benjamin Knoth wrote:
>
>> Am 08.02.2011 12:38, schrieb Brett Porter:
>>>
>>> On 08/02/2011, at 8:00 PM, Benjamin Knoth wrote:
>>>
>>>> Hi Brett,
>>>> this is the output.
>>>
>>> Everything looks normal here - you're not running out of memory, and the scans are quick.
>>>
>>> You said the peaks coincided with the database scan in 1.3.1 - is that also the case in 1.3.3? Do they still last 12 minutes?
>>
>> No the last output in the log file which i send you was repeated 4 times
>> with a difference of +- 2 seconds. But since 5 hours it runs with 100%
>> cpu usage.
>
> Sorry, I'd like to clarify I'm understanding correctly. What I've seen is the hourly scans completing in ~1-2 minutes (10 seconds for the repository scan, 50 seconds for the database scan). The status panel you showed had nothing queued. However, you're still seeing continuous 100% usage of the application for over 5 hours?
>
> How many requests is the box receiving? It doesn't appear you've got any problematic background processing, so it might be request load.
>
> Or is it possible that something else on the VM is constraining the resources it has? Or perhaps forcing swap space to be used?
>
>>
>> It's possible that i need 2 cores of cpu or should i change the memory
>> usage in archiva more than 1 GB ram. This VM have 4 GB Ram and 1 Core of
>> the CPU.
>
> 1 core should be fine. The status page showed only 144M of the RAM had been allocated (and only 48M used) out of the 991M you set aside, so that's not the issue.
>
> The only other investigation I can think of is to do a thread dump (./bin/maestro dump). If you are wanting to analyze it closely you could connect a profiler (like yourkit) to the running instance as well.
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
--
Benjamin Knoth
Max Planck Digital Library (MPDL)
Systemadministration
Amalienstrasse 33
80799 Munich, Germany
http://www.mpdl.mpg.de
Mail: knoth@mpdl.mpg.de
Phone: +49 89 38602 202
Fax: +49-89-38602-280
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
On 08/02/2011, at 11:57 PM, Benjamin Knoth wrote:
> Am 08.02.2011 12:38, schrieb Brett Porter:
>>
>> On 08/02/2011, at 8:00 PM, Benjamin Knoth wrote:
>>
>>> Hi Brett,
>>> this is the output.
>>
>> Everything looks normal here - you're not running out of memory, and the scans are quick.
>>
>> You said the peaks coincided with the database scan in 1.3.1 - is that also the case in 1.3.3? Do they still last 12 minutes?
>
> No the last output in the log file which i send you was repeated 4 times
> with a difference of +- 2 seconds. But since 5 hours it runs with 100%
> cpu usage.
Sorry, I'd like to clarify I'm understanding correctly. What I've seen is the hourly scans completing in ~1-2 minutes (10 seconds for the repository scan, 50 seconds for the database scan). The status panel you showed had nothing queued. However, you're still seeing continuous 100% usage of the application for over 5 hours?
How many requests is the box receiving? It doesn't appear you've got any problematic background processing, so it might be request load.
Or is it possible that something else on the VM is constraining the resources it has? Or perhaps forcing swap space to be used?
>
> It's possible that i need 2 cores of cpu or should i change the memory
> usage in archiva more than 1 GB ram. This VM have 4 GB Ram and 1 Core of
> the CPU.
1 core should be fine. The status page showed only 144M of the RAM had been allocated (and only 48M used) out of the 991M you set aside, so that's not the issue.
The only other investigation I can think of is to do a thread dump (./bin/maestro dump). If you are wanting to analyze it closely you could connect a profiler (like yourkit) to the running instance as well.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 08.02.2011 12:38, schrieb Brett Porter:
>
> On 08/02/2011, at 8:00 PM, Benjamin Knoth wrote:
>
>> Hi Brett,
>> this is the output.
>
> Everything looks normal here - you're not running out of memory, and the scans are quick.
>
> You said the peaks coincided with the database scan in 1.3.1 - is that also the case in 1.3.3? Do they still last 12 minutes?
No the last output in the log file which i send you was repeated 4 times
with a difference of +- 2 seconds. But since 5 hours it runs with 100%
cpu usage.
It's possible that i need 2 cores of cpu or should i change the memory
usage in archiva more than 1 GB ram. This VM have 4 GB Ram and 1 Core of
the CPU.
>
> Perhaps you can reduce the database scanning interval to a less frequent time (note that in 1.4, we'll be removing that overhead altogether).
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
Benjamin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJNUT3AAAoJEALVkoFaZmWjfHAP/03j/YpIdNpe2htdUEoc0d7H
Lin6qibUbyNPENgQyQ7SaK8F+0g0Olk2nTVX6uUrjSDeTtnMbz8gnW8lcz1Ps1rB
Me3x3jLq9M81cQOQp+YjyBtgDmmHUGb+NSusOO27nWPD+Usg1ZQYecNu4nPv18FE
K0I4pWYgqUpIbo/utxGnDAhjcpAjwaJmBW6CKeMlLkPBPEkFMu/LtrbX6FBKnPO9
q4m9/5T1+MROHVL+UC+bPsjyfRyLB1LOxdAcRbny+B4Ne7gxPBOLvZmZ/deb3pI+
vI24Esnx1A9alByIAmD1o+QS8Ah78nhsk8dg+WUzzDXLHq78SI7NjDfUCfVL8d/O
nnpryUfionSrGDNIkt7niMXRNh//oJ1L7aX1GqFO9yVkUtlvPgY6as573P7/xKlT
pFKib1ErBT4RYVp5Y7fUkNHQEGsyc+ca7bSxVXd6CzZ/Cbxmeefri18wEcdB5jaV
jQCVwbby1J6ER1iNObAu2cv/sLrUDxyJTHsjCA2E/C0BRjCAVy+9VYGbdA8pOtuW
TQqeNohZBaAkLlAmGNDwFCpWVUlSv+fBbe0F/MZm0yjgOIUQn+QPKd39mdde61Ql
GjXn7dL7X9YsMdm8gIWMeuxpG01BrJtMEgpaN0IwSQmAvr4sYi5lt332QCQrGJ57
lbvYyIXUshtLG4SwLOWA
=D5hi
-----END PGP SIGNATURE-----
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
On 08/02/2011, at 8:00 PM, Benjamin Knoth wrote:
> Hi Brett,
> this is the output.
Everything looks normal here - you're not running out of memory, and the scans are quick.
You said the peaks coincided with the database scan in 1.3.1 - is that also the case in 1.3.3? Do they still last 12 minutes?
Perhaps you can reduce the database scanning interval to a less frequent time (note that in 1.4, we'll be removing that overhead altogether).
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Benjamin Knoth <kn...@mpdl.mpg.de>.
Hi Brett,
this is the output.
Am 08.02.2011 09:46, schrieb Brett Porter:
> There was an issue before 1.3.3 about this at the end of a scan that should have been fixed. Do you get anything after the last horizontal rule?
>
That's the log of the last hour.
2011-02-08 08:59:57,182 [btpool0-0] INFO
com.opensymphony.xwork2.validator.Action
ValidatorManagerFactory - Detected AnnotationActionValidatorManager,
initializing
it...
2011-02-08 09:00:00,105 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Executing task from
queue with
job name: RepositoryTask [repositoryId=snapshots, resourceFile=null,
scanAll=fals
e, updateRelatedArtifacts=false]
2011-02-08 09:00:00,105 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Executing task from
queue with job
name: DatabaseTask
2011-02-08 09:00:00,145 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Started: [snapshots]
/data/archiva/rep
ositories/snapshots
2011-02-08 09:00:00,157 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
unprocessed artifac
ts
2011-02-08 09:00:00,440 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating processed
artifacts
2011-02-08 09:00:12,904 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Finished: [snapshots]
/data/archiva/re
positories/snapshots
2011-02-08 09:00:12,905 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Finished repository
task:
.\ Scan of snapshots \.__________________________________________
Repository Dir : /data/archiva/repositories/snapshots
Repository Name : Archiva Managed Snapshot Repository
Repository Layout : default
Known Consumers : (1 configured)
update-db-artifact
Invalid Consumers : <none>
Duration : 12 Seconds 759 Milliseconds
When Gathered : 08.02.11 09:00
Total File Count : 22879
Avg Time Per File :
______________________________________________________________
2011-02-08 09:00:20,013 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Executing task from
queue with
job name: RepositoryTask [repositoryId=internal, resourceFile=null,
scanAll=false
, updateRelatedArtifacts=false]
2011-02-08 09:00:20,312 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Started: [internal]
/data/archiva/repo
sitories/internal
2011-02-08 09:00:30,248 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Finished: [internal]
/data/archiva/rep
ositories/internal
2011-02-08 09:00:30,248 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Finished repository
task:
.\ Scan of internal \.__________________________________________
Repository Dir : /data/archiva/repositories/internal
Repository Name : Archiva Managed Internal Repository
Repository Layout : default
Known Consumers : (1 configured)
update-db-artifact
Invalid Consumers : <none>
Duration : 9 Seconds 936 Milliseconds
When Gathered : 08.02.11 09:00
Total File Count : 55540
Avg Time Per File :
______________________________________________________________
2011-02-08 09:00:51,418 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Finished database task
in 51261ms.
> It might be that your index is very large (though it shouldn't be for these repository sizes). What is the size of the .index and .indexer directories?
du -hs .index
9.0M .index
du -hs .indexer/
9.5M .indexer/
>
> What do you see on the system status page during the high CPU usage?
Administration - System Status
Queues
Queue Size
database-update 0
indexing 0
repository-scanning 0
Repository Scans Currently in Progress
No scans in progress.
Caches
Cache Size Hits Misses Hit Ratio
operations 25 11 50 18% Flush
users 8 254 21 92% Flush
resources 2 2 4 33% Flush
url-failures-cache 186 0 0 0% Flush
userPermissions 2 249 12 95% Flush
effective-project-cache 102 233705 102 100% Flush
roles 13 4 26 13% Flush
permissions 31 14 62 18% Flush
effectiveRoleSet 0 0 0 0% Flush
userAssignments 0 2 4 33% Flush
ehcache 0 0 0 0% Flush
keys 1 0 4 0% Flush
Memory Usage
48M/144M (Max: 991M)
Current Time
Tue Feb 08 09:43:11 CET 2011
>
> Thanks,
> Brett
>
Thanks,
Benjamin
> On 08/02/2011, at 7:13 PM, Benjamin Knoth wrote:
>
>>
> Hi all,
> 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.
>
> 2011-02-08 07:00:13,123 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Started: [snapshots]
> /data/archiva/rep
> ositories/snapshots
> 2011-02-08 07:00:15,778 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> processed artifacts
> 2011-02-08 07:00:18,778 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Finished: [snapshots]
> /data/archiva/re
> positories/snapshots
> 2011-02-08 07:00:18,778 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Finished
> repository task:
> .\ Scan of snapshots \.__________________________________________
> Repository Dir : /data/archiva/repositories/snapshots
> Repository Name : Archiva Managed Snapshot Repository
> Repository Layout : default
> Known Consumers : (1 configured)
> update-db-artifact (Total: 2592ms; Avg.: 1296;
> Count: 2)
> Invalid Consumers : <none>
> Duration : 5 Seconds 654 Milliseconds
> When Gathered : 2/8/11 7:00 AM
> Total File Count : 22879
> Avg Time Per File :
> ______________________________________________________________
> 2011-02-08 07:00:49,254 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Finished database task
> in 49230ms.
> 2011-02-08 08:00:00,022 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Executing task from
> queue with job
> name: DatabaseTask
> 2011-02-08 08:00:00,022 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> unprocessed artifac
> ts
> 2011-02-08 08:00:00,046 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Executing task
> from queue with
> job name: RepositoryTask [repositoryId=internal, resourceFile=null,
> scanAll=false
> , updateRelatedArtifacts=false]
> 2011-02-08 08:00:00,119 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Started: [internal]
> /data/archiva/repo
> sitories/internal
> 2011-02-08 08:00:02,229 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> processed artifacts
> 2011-02-08 08:00:10,753 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Finished: [internal]
> /data/archiva/rep
> ositories/internal
> 2011-02-08 08:00:10,753 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Finished
> repository task:
> .\ Scan of internal \.__________________________________________
> Repository Dir : /data/archiva/repositories/internal
> Repository Name : Archiva Managed Internal Repository
> Repository Layout : default
> Known Consumers : (1 configured)
> update-db-artifact
> Invalid Consumers : <none>
> Duration : 10 Seconds 634 Milliseconds
> When Gathered : 2/8/11 8:00 AM
> Total File Count : 55540
> Avg Time Per File :
> ______________________________________________________________
>
> What should i do to resolve this problem.
>
> Best regards
>
> Benjamin
>
>
>>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
Re: 100 %cpu usage
Posted by Brett Porter <br...@apache.org>.
There was an issue before 1.3.3 about this at the end of a scan that should have been fixed. Do you get anything after the last horizontal rule?
It might be that your index is very large (though it shouldn't be for these repository sizes). What is the size of the .index and .indexer directories?
What do you see on the system status page during the high CPU usage?
Thanks,
Brett
On 08/02/2011, at 7:13 PM, Benjamin Knoth wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
> 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.
>
> 2011-02-08 07:00:13,123 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Started: [snapshots]
> /data/archiva/rep
> ositories/snapshots
> 2011-02-08 07:00:15,778 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> processed artifacts
> 2011-02-08 07:00:18,778 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Finished: [snapshots]
> /data/archiva/re
> positories/snapshots
> 2011-02-08 07:00:18,778 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Finished
> repository task:
> .\ Scan of snapshots \.__________________________________________
> Repository Dir : /data/archiva/repositories/snapshots
> Repository Name : Archiva Managed Snapshot Repository
> Repository Layout : default
> Known Consumers : (1 configured)
> update-db-artifact (Total: 2592ms; Avg.: 1296;
> Count: 2)
> Invalid Consumers : <none>
> Duration : 5 Seconds 654 Milliseconds
> When Gathered : 2/8/11 7:00 AM
> Total File Count : 22879
> Avg Time Per File :
> ______________________________________________________________
> 2011-02-08 07:00:49,254 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Finished database task
> in 49230ms.
> 2011-02-08 08:00:00,022 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Executing task from
> queue with job
> name: DatabaseTask
> 2011-02-08 08:00:00,022 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> unprocessed artifac
> ts
> 2011-02-08 08:00:00,046 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Executing task
> from queue with
> job name: RepositoryTask [repositoryId=internal, resourceFile=null,
> scanAll=false
> , updateRelatedArtifacts=false]
> 2011-02-08 08:00:00,119 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Started: [internal]
> /data/archiva/repo
> sitories/internal
> 2011-02-08 08:00:02,229 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> processed artifacts
> 2011-02-08 08:00:10,753 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Finished: [internal]
> /data/archiva/rep
> ositories/internal
> 2011-02-08 08:00:10,753 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Finished
> repository task:
> .\ Scan of internal \.__________________________________________
> Repository Dir : /data/archiva/repositories/internal
> Repository Name : Archiva Managed Internal Repository
> Repository Layout : default
> Known Consumers : (1 configured)
> update-db-artifact
> Invalid Consumers : <none>
> Duration : 10 Seconds 634 Milliseconds
> When Gathered : 2/8/11 8:00 AM
> Total File Count : 55540
> Avg Time Per File :
> ______________________________________________________________
>
> What should i do to resolve this problem.
>
> Best regards
>
> Benjamin
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQIcBAEBAgAGBQJNUPs+AAoJEALVkoFaZmWjK/4QAKEU4TbPjTfmqbPbpUC5Wfxp
> ivZ9epIlwX5DkMVj73weIdTC0Xs2JL/qx6smdM9EN0npe+LYSqOFle+1QAkJFc9t
> w6XyUSy0YvIkNHKy0HmNxJyiII9/DXdnfnmawfYBrPB2XUbR1aRmqTsH9Wo7uy3K
> NP2x1KaAGTZkMHpB8lBH2wVn4Z/eKjbU9+OX0XspmWp3ukheCC8GgJuv4zmbH22E
> Yu3vjwOkKfCV7LkE0Gnq0BFrdn3J9xOEodOQWXB2au6UCpIQa1eYSh2oorRMoajR
> 5DEkTjYsy44YLLHIl8m7xUQMmVXyLx49dwsB1kdHXxpO5PKyI/jYFhc+nP1qRiAZ
> h1zHQZvVklBrFRTWb4GfIE0IL9oUubWQlXHtq5QAR+C1uIJSdIvX1KePaRN2EA1k
> lYh/wZ4kYlvcU/1UAhyfP79eDJgQcnyGrk9ZJeFWJ9+KkvJ5CFoajjlYlP3SECP3
> Y0xSOneJo0VWWbKAv4EycJ9Amk2DjenUpmndU7qazXj+v/C7z6mKHxtz6VeOQu2X
> 8n0gi99VUQ3EcOBlrAI+ccv8/45vKNHNGiamoTnnNAbCwXDjJXBHU9mY2IxXYVPt
> 9R4Gd6WaJsk0tHLK4h3U9NgywJObzWcAUHqJEx2s+br3ptgidA843HP27FHvTJyG
> 8+Yjn5db9IrK1nkOHNWV
> =IRy/
> -----END PGP SIGNATURE-----
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter