[
https://issues.apache.org/activemq/browse/CAMEL-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2484.
--------------------------------
Resolution: Fixed
Stan that is great.
Yeah it was a bad move by Claus to enlist Producer's for management ;). Wonder
how we slipped this for 2 releases?
I actually think we should just enlist producers only if CamelContext is in
state of starting. Then we get the starting Producers enlisted which are the
ones in your routes (eg in the to(xxx)).
> 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.
