You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/02/06 06:43:28 UTC

[jira] Commented: (MRM-682) Archiva runs out of heap memory

    [ http://jira.codehaus.org/browse/MRM-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122529 ] 

Brett Porter commented on MRM-682:
----------------------------------

I spent some time profiling Archiva back in 0.9 to ensure there were no instances of this, particularly during scanning.

With the current architecture it should be easy to identify a leak.

Regardless - does disabling certain things you don't need help? I'd be interested to see what happens if the consumers were turned off and just proxying/webdav was in place.

> Archiva runs out of heap memory
> -------------------------------
>
>                 Key: MRM-682
>                 URL: http://jira.codehaus.org/browse/MRM-682
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0, 1.0.1, 1.1
>            Reporter: James William Dumay
>            Priority: Critical
>         Attachments: m2proxy.20080204.tar.gz, maven.atlassian.com-log-20080203-0125.tgz, maven.atlassian.com-logs-20080203-0745.tgz
>
>
> Archiva appears to run out of heap memory frequently and the service crashes.
> 512mb should be more than enough.

-- 
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