Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.0, 1.0.1, 1.1
-
Fix Version/s: 1.1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Archiva appears to run out of heap memory frequently and the service crashes.
512mb should be more than enough.
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.