[
https://jira.codehaus.org/browse/MRM-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345588#comment-345588
]
Sascha Vogt commented on MRM-1837:
----------------------------------
We had a memory issue and the gathered heap dump showed 169k instances of
XASessionImpl and 84k instances of each
RepositoryPurgeConsumer, NexusIndexerConsumer, MetadataUpdaterConsumer,
DuplicateArtifactsConsumer, ArchivaMetadataCreationConsumer,
ArtifactMissingChecksumsConsumer and AutoRemoveConsumer
The XASessionImpls were responsible for 84% heap usage, according to the
Eclipse Memory Analyzer (we have set Archiva to 4 GB)
>From the comment of RepositoryContentConsumer:
* olamy: TODO/FIXME we must review this api, in the current situation we use
prototype beans rather than singletons
* this is a bit memory consuming the better will be to ConsumerContext bean to
transport repository context etc...
> DefaultArchivaConfiguration holds references to classes
> -------------------------------------------------------
>
> Key: MRM-1837
> URL: https://jira.codehaus.org/browse/MRM-1837
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 2.0.0, 2.0.1
> Reporter: Olivier Lamy
> Priority: Critical
> Fix For: 2.1.0
>
>
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
