camel-dev mailing list archives

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


Claus Ibsen commented on CAMEL-1771:

I actually think we should not *store* the endpoints that have lenient properties, such as
*http*. Then we wont store them in the CamelContext.

So if you need such an endpoint its created on demand when you call the {{getEndpoint(uri)}}
So when you do as you have millions http endpoints that are different it wont be added to
Camel and also not in JMX.

In the future we could add the first in JMX to have a single entry there so we later can track
number of invocations to this endpoint and more.
But all the JMX stuff is slated for an overhaul in 2.1

> ProducerCache should be limited to not eat memory (was: recipientList leaks memory)
> -----------------------------------------------------------------------------------
>                 Key: CAMEL-1771
>                 URL:
>             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.

View raw message