You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Timothy Ward (JIRA)" <ji...@apache.org> on 2016/09/06 23:49:21 UTC

[jira] [Commented] (ARIES-1604) Aries async Thread leak

    [ https://issues.apache.org/jira/browse/ARIES-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468986#comment-15468986 ] 

Timothy Ward commented on ARIES-1604:
-------------------------------------

I would hope that these threads would be terminated when the promise is garbage collected, but we could also be a little more efficient with the executor usage (for example by reusing the executor when chaining).

> 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
>
> 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)