[
https://issues.apache.org/activemq/browse/CAMEL-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57678#action_57678
]
Stan Lewis commented on CAMEL-2484:
-----------------------------------
So the problem is thanks to the RecipientList. It obtains a producer from the
ProducerCache directly, in this case the ProducerCache doesn't actually cache
the producer, it just creates a new producer and adds it to
DefaultCamelContext.servicesToClose, which winds up holding thousands of
MinaProducer objects. It looks like really the RecipientList is better off
just calling Endpoint.createProducer() and avoiding the producer cache
altogether, *or* the RecipientList could ensure that each producer is removed
from the CamelContext (am testing this now just to be sure it fixes the OOM)
*or* the RecipientList could use a bit of a re-factoring so that it uses the
ProducerCache properly.
> camel-mina - Using close session could potentially cause memory to be not
> released
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-2484
> URL: https://issues.apache.org/activemq/browse/CAMEL-2484
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-mina
> Affects Versions: 2.1.0, 2.2.0
> Reporter: Claus Ibsen
> Assignee: Stan Lewis
> Fix For: 2.3.0
>
> Attachments: camel-mina-outofmemory-example.zip,
> java_pid26327.hprof.tar.gz
>
>
> See nabble
> http://old.nabble.com/SocketSessionImpl-in-Mina-component-retained-in-memory-indefinitely-ts27624487.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
