[
https://issues.apache.org/activemq/browse/CAMEL-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1771.
--------------------------------
Resolution: Fixed
trunk: 789593.
1.x: 789598.
Andres can you try again with latest code? I have fixed this and also the JMX
issue as well, so Camel will not register all the http endpoints.
So you do *not* need your own custom naming strategy anymore.
The fix is for both 1.6.2 and 2.0
> 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.
