You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org> on 2007/02/14 15:54:22 UTC
[jira] Commented: (MRM-239) OutOfMemory error when running Arhiva
for days at a time
[ http://jira.codehaus.org/browse/MRM-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87588 ]
Joakim Erdfelt commented on MRM-239:
------------------------------------
After running archiva through YourKit Java Profiler, I found 4 places that need help .... badly.
# DefaultReportingStore
# DirectoryScanner
# DefaultArtifactDiscoverer
# DefaultMetadataDiscoverer
What it comes down to is *bad* memory utilization, with the ability to *spike* 22MB to 45MB in a few seconds depending on what you are doing.
The Discoverer process is the one most at fault, the whole notion of using the DirectoryScanner and maintaining a list of Files in memory for the entire repository is just insane. And this Discoverer process can exist in multiple places at once, using even more memory that is needed.
The DefaultReportStore uses an XML based store for failures, warnings, and notices about artifacts and metadata. This Maps within Map of information kept in memory can also spike the memory very agressively.
I have started a branch - https://svn.apache.org/repos/asf/maven/archiva/branches/archiva-MRM-239 to work on correcting these deficiencies in the archiva codebase.
Watch for changes in archiva-discoverer and archiva-reports-standard.
> 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
> Components: system
> Affects Versions: 1.0
> Environment: Linux and Mac OS X
> Reporter: Greg Luck
> Assigned To: Joakim Erdfelt
> 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