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

Posted to issues@camel.apache.org by "John Poth (Jira)" <ji...@apache.org> on 2019/09/20 15:12:00 UTC

[jira] [Assigned] (CAMEL-14000) ServicePool can cause memory leak

     [ https://issues.apache.org/jira/browse/CAMEL-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Poth reassigned CAMEL-14000:
---------------------------------

    Assignee: John Poth

> ServicePool can cause memory leak
> ---------------------------------
>
>                 Key: CAMEL-14000
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14000
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.24.2, 3.0.0.RC1
>            Reporter: John Poth
>            Assignee: John Poth
>            Priority: Major
>
> The [ServicePool|[https://github.com/apache/camel/blob/master/core/camel-base/src/main/java/org/apache/camel/impl/engine/ServicePool.java#L50]] or (DefaultServicePool in 2.x) uses a unbounded ConcurrentHashMap to cash producers. This can cause memory leaks in highly dynamic routes using recipient lists creating many temporary endpoint which will never be evicted even when the route stops. Even though workarounds exists, we might consider using an LRUCache for eviction.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)