[
https://issues.apache.org/jira/browse/AMQ-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307943#comment-14307943
]
Timothy Bish commented on AMQ-5564:
-----------------------------------
Previous fixes that have gone in were meant to ensure that resources linked to
the pooled session and connection which should be closed or deleted such as
temp destinations happened correctly at connection close even though the
connection itself was kept in the pool for future use. The issue here is that
the anonymous producer that is created for a pooled session is being lost along
the way and a new one gets created every time an existing session is reused in
the pool.
> activemq-pool - Either adds new mbeans or add/remove pair of mbean for each
> producer in use
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-5564
> URL: https://issues.apache.org/jira/browse/AMQ-5564
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-pool
> Affects Versions: 5.10.1, 5.11.0
> Reporter: Claus Ibsen
> Assignee: Timothy Bish
> Attachments: amq-5100.png, amq-5101.png, amq-5110.png
>
>
> On the AMQ dev mailing list we have talked about a new issue.
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743.html
> I found out that using the camel-example-management, which has an embedded
> AMQ broker and using Camel with the VM transport to produce/consume messages,
> then there is mbean issues.
> It works fine in AMQ 5.10.0. But is wrong in AMQ 5.10.1 and 5.11.0.
> See the attached screenshots.
> Notice how the mbean tree for dynamic producers keeps growing for 5.10.1 and
> 5.11.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
