You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/23 10:12:00 UTC

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

     [ https://issues.apache.org/jira/browse/CAMEL-14000?focusedWorklogId=316590&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-316590 ]

ASF GitHub Bot logged work on CAMEL-14000:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Sep/19 10:11
            Start Date: 23/Sep/19 10:11
    Worklog Time Spent: 10m 
      Work Description: johnpoth commented on pull request #3186: CAMEL-14000 - remove Endpoint from Map when corresponding Pool is empty
URL: https://github.com/apache/camel/pull/3186
 
 
   https://issues.apache.org/jira/browse/CAMEL-14000
   
   Thanks!
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 316590)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)