aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (JIRA)" <>
Subject [jira] [Commented] (ARIES-1604) Aries async Thread leak
Date Wed, 07 Sep 2016 13:20:20 GMT


Timothy Ward commented on ARIES-1604:

> I thought the same when I saw the implementation but they're not unfortunately. Anyway,
you're right I think. It could be more efficient to reuse the same executor instance for the

I've checked this, and because Executors.newSingleThreadExecutor() is used then the Thread
*will* be stopped when the Promise is garbage collected. The problem will show up when the
Promise creation rate it too high, which should be much less of a problem in the latest snapshot.

The snapshot versions of promise.api, async.impl and async are now 1.1.0-SNAPSHOT due to the
change in API.

> Aries async Thread leak
> -----------------------
>                 Key: ARIES-1604
>                 URL:
>             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

View raw message