[
https://issues.apache.org/activemq/browse/CAMEL-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57699#action_57699
]
Stan Lewis commented on CAMEL-2484:
-----------------------------------
@Claus, thanks! I'll look into getting the RecipientList working properly with
the cache, did a long-running test last night with Johan's test case just to
verify that's the issue, and I didn't get any OOMs, but creating/destroying the
producers with each exchange is definitely expensive and can cause other
problems.
@Johan, in case you need something running right away you should be able to
avoid this problem for now by replacing the RecipientList with a simple
processor that looks at the header and uses a producer template to send on the
message, the producer template uses the cache properly. I'll of course update
the ticket when I get this fixed...
> 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.
