[ http://jira.codehaus.org/browse/MRM-239?page=comments#action_81614 ]
Joakim Erdfelt commented on MRM-239:
------------------------------------
I can conform this.
Happened to me with Archiva running on Linux.
{code}
[EMAIL PROTECTED] uname -a
Linux buildux 2.6.17-10-server #2 SMP Fri Oct 13 18:47:26 UTC 2006 i686
GNU/Linux
[EMAIL PROTECTED] java -version
java version "1.5.0_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
Java HotSpot(TM) Client VM (build 1.5.0_08-b03, mixed mode, sharing)
{code}
I run using the following command line.
{code}
[EMAIL PROTECTED]/java/jetty-6.0.2]$ ls -la webapps-plus
total 8
drwxr-xr-x 2 archiva archiva 4096 2006-11-28 17:50 .
drwxrwxr-x 18 archiva archiva 4096 2006-11-28 17:50 ..
drwxrwxrwx 1 archiva archiva 4096 2006-11-28 17:50 archiva
[EMAIL PROTECTED]/java/jetty-6.0.2]$ java -Xmx256m -jar start.jar etc/jetty.xml
etc/jetty-plus.xml
{code}
Note, it doesn't matter how much memory i give it, (tested up to 1024m) it will
still fail with OOM, it just takes longer with more memory.
Some details of the size of my repository.
{code}
[archiva@/home/repo1/ibiblio]$ find . -type f | wc -l
156944
[archiva@/home/repo1/ibiblio]$ find . -type d | wc -l
22357
{code}
I also captured a stack trace.
{code}
2006-11-30 19:22:22,438 [pool-1-thread-1] ERROR
RepositoryIndexRecordFactory:standard - Error reading artifact file, omitting
from index: error in opening zip file
2006-11-30 19:22:22,554 [pool-1-thread-1] ERROR
RepositoryIndexRecordFactory:standard - Error reading artifact file, omitting
from index: error in opening zip file
2006-11-30 19:28:22,561 [Thread-12] ERROR TaskQueueExecutor:indexer -
Error executing task
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.lang.OutOfMemoryError: Java heap space
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127)
Caused by: java.lang.OutOfMemoryError: Java heap space
2006-11-30 20:00:03,847 [pool-1-thread-1] DEBUG ReportExecutor
- Reading previous report database Repository Health from repository central
2006-11-30 20:23:53,246 [Thread-12] ERROR TaskQueueExecutor:indexer -
Error executing task
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.lang.OutOfMemoryError: Java heap space
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127)
Caused by: java.lang.OutOfMemoryError: Java heap space
{code}
Since it seemd to be 'reading previous report database', i decided to poke
around ...
{code}
[archiva@/home/repo1/ibiblio/.reports]$ ls -la
total 9612
drwxrwxrwx 2 repo1 repo1 4096 2006-11-29 15:13 .
drwxrwxr-x 617 repo1 repo1 12288 2006-09-05 19:44 ..
-rw-r--r-- 1 archiva archiva 9809591 2006-11-30 19:21 health-report.xml
[archiva@/home/repo1/ibiblio/.reports]$ wc -l health-report.xml
123651 health-report.xml
[archiva@/home/repo1/ibiblio/.reports]$ xmllint --noout health-report.xml ;
echo $?
0
{code}
I'll attach my health-report.xml to this jira, it might prove useful.
> OutOfMemory error when running Arhiva for days at a time
> --------------------------------------------------------
>
> Key: MRM-239
> URL: http://jira.codehaus.org/browse/MRM-239
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-beta-1
> Environment: Linux and Mac OS X
> Reporter: Greg Luck
> Fix For: 1.0-beta-1
>
>
> I have been running Archiva as it existed in snapshot 20 November 2006.
> When running in Tomcat with the standard memory setting it fails after a few
> days.
> Increasing -Xmx=128m increases the time but it still gets and OutOfMemory
> error after a few days.
> This is with no activity. I came back today after the weekend and hit refresh
> on a Pom page and it gave the OOM. It seems to be time dependent. At home I
> have been running it on Mac OS X. I saw an OutOfMemory error after a week. I
> did even go to a page to check it. The running console had it.
> To reproduce simply run up archiva and leave it running.
> We are working around with a nightly restart.
--
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
