[
https://issues.apache.org/jira/browse/ARIES-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549091#comment-15549091
]
Paul Thevenot commented on ARIES-1604:
--------------------------------------
The issue is still there if you use the fireAndForget method because we should
replace
{code:java|title=MethodCall.java}
PromiseImpl<Void> cleanup = new PromiseImpl<Void>();
{code}
by
{code:java|title=MethodCall.java}
PromiseImpl<Void> cleanup = new PromiseImpl<Void>(executor);
{code}
I think. Could it be possible to make the change?
> Aries async Thread leak
> -----------------------
>
> Key: ARIES-1604
> URL: https://issues.apache.org/jira/browse/ARIES-1604
> Project: Aries
> Issue Type: Bug
> Affects Versions: async-1.0.2
> Reporter: Paul Thevenot
> Fix For: async-1.1.0
>
>
> The async service with repeated tasks leads to an OutOfMemoryError because
> too many threads are created and we achieve the maximum number of threads of
> the host (unable to create new native thread).
> The leak seems to come from the PromiseImpl. For each Promise instantiated,
> we do create a new SingleThreadExecutor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
