camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1771) ProducerCache should be limited to not eat memory (was: recipientList leaks memory)
Date Mon, 29 Jun 2009 15:56:07 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52557#action_52557
] 

Claus Ibsen commented on CAMEL-1771:
------------------------------------

Yeah CamelContext also holds a list of all endpoints created. I guess we should use a LRUCache
as well to avoid high memory usages.

Another idea is to not add these endpoints to the CamelContext internal list at all as you
will not re-use them later anyway.
But I am working on a patch for the JMX console right now. Only registering 1 endpoint for
all the https.

> ProducerCache should be limited to not eat memory (was: recipientList leaks memory)
> -----------------------------------------------------------------------------------
>
>                 Key: CAMEL-1771
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1771
>             Project: Apache Camel
>          Issue Type: Bug
>    Affects Versions: 1.4.0, 1.5.0, 1.6.0, 1.6.1, 2.0-M2
>            Reporter: Andres
>            Assignee: Claus Ibsen
>            Priority: Critical
>             Fix For: 1.6.2, 2.0.0
>
>
> I found that RecipientList leaks memory .
> The problem is that RecipientList stores endpoints in producerCache and cache key computed
by using getEndpointUri. If endpoint uris are unique ( as we have ) then every new entry will
stored in cache and will never released.
> In example we are using recipientList  to send messages to the external http server,
every url contains unique query parameters therefor every recipientList entry will create
new producer ant that producer will stored in producerCache.
> In our system recipientList wlil leak about 20M per day
> Unfortunately I was unable to find any workaround 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message