[ http://jira.codehaus.org/browse/MRM-239?page=comments#action_81817 ]
pkernevez commented on MRM-239:
-------------------------------
We have exactly the same issue.
I first tried to increase memory (Archiva and Jira are the both application
deployed in Tomcat), but I only delayed (3-4 days) the OutOfMemory, we now use
_-verbose:gc -Xms256M -Xmx1500M -XX:PermSize=64m -XX:MaxPermSize=192m_
OS : 2.4.21-32.0.1.EL
Container: Tomcat 5.5.20
JVM: Sun 1.5.0_09
Maven repo : only Maven2
ArchivaDb: Derby
Archiva.xml
{noformat}
<?xml version="1.0" encoding="UTF-8"?><configuration>
<repositories>
<repository>
<urlName>FTInterne</urlName>
<directory>/etc/udd/maven/repositories/FTInterne</directory>
<includeSnapshots>true</includeSnapshots>
<id>FTInterne</id>
<name>FTInterne</name>
</repository>
<repository>
<urlName>FTPublicMirror</urlName>
<directory>/etc/udd/maven/repositories/FTPublicMirror</directory>
<includeSnapshots>true</includeSnapshots>
<id>FTPublicMirror</id>
<name>FTPublicMirror</name>
</repository>
</repositories>
<proxiedRepositories>
<proxiedRepository>
<url>http://repo1.maven.org/maven2/</url>
<managedRepository>FTPublicMirror</managedRepository>
<checksumPolicy>warn</checksumPolicy>
<useNetworkProxy>true</useNetworkProxy>
<id>m2-central-repository</id>
<name>m2-central-repository</name>
</proxiedRepository>
</proxiedRepositories>
<localRepository>/etc/udd/maven/repositories/LocalRepo</localRepository>
<indexPath>/var/udd/maven/index</indexPath>
<indexerCronExpression>0 * * * * ?</indexerCronExpression>
<proxy>
<username>XXXX</username>
<password>YYYY</password>
<host>ZZZZ</host>
</proxy>
</configuration>
{noformat}
> 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
>
> Attachments: health-report.xml
>
>
> 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
