[
https://issues.apache.org/jira/browse/ARIES-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470662#comment-15470662
]
Timothy Ward commented on ARIES-1603:
-------------------------------------
Could you include a sample of the usage here? I'm very surprised to hear that
you're creating so many mediated classes, as you're really supposed to create
one and keep using it (it's thread safe). In addition the Async service doesn't
hold on to the mediator object except when the async task is executing.
Also, what sort of load management are you doing in the application? Is it
possible that the memory problem is due to a large and growing queue of
asynchronous tasks waiting to execute?
> Aries async classloader leak
> ----------------------------
>
> Key: ARIES-1603
> URL: https://issues.apache.org/jira/browse/ARIES-1603
> Project: Aries
> Issue Type: Bug
> Affects Versions: async-1.0.2
> Reporter: Paul Thevenot
>
> Using the async service with repeated tasks during one hour leads to an out
> of memory. It's due to the very large amount of class loaded (in 10 min we
> get 20000 classes loaded). The metaspace is growing indefinitely.
> It seems to come from the privMediate method of the AsyncService where the
> classloader of the target service is cloned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
