Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
1.4-M4
-
None
-
Linux SLES 11 86_64
Description
Perhaps some duplicate of MRM-1741 (but no activity since 6 months => openend a new)
We are using Archiva 1.4-M4 for our company, and we found some memory problem usage on this version.
It seems not to be a "big problem", because there is not directly a OutOfMemory, the Jetty server becomes very slow before. Symptom from CI platorm (for exemple) :
Server returned HTTP response code: 502 for URL: http://[url]/repository/[repoName]/[grouId]/[artifactId]/[version]/maven-metadata.xml
Informations about volumetry :
Requests by day (wc -l request-XXX.log) : 430000 (average)
Company repositories (Total File Count from Stats in Repositories menu) :
- company-releases : 574771
- company-snapshots : 118905
- proxied-releases : 232626
- proxied-snapshots : 2136
- extra-libs : 9232
- commercial-libs : 4587
- Total : 950000
Note : Option "Skip Packed Index creation" activated on each repositories.
Analysis :
The GC grow up during the week :
The invocation to GC grow up when memory is short :
Before the problem, we can see the impact (difficulty to garbage memory) :
After a application restart, the common usage is less than 2Go :
=> So the supposition is a little memory leak.
A solution could be some cache time reduction or SoftReference/WeakReference usage.
Today I have not more information about problem, restart was urgent, and analysis a 4Go HeapDump a little difficult.
I will take HeapDumps the next week to give some detail about memory usage.