[
https://issues.apache.org/jira/browse/AMQ-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308100#comment-14308100
]
Arthur Naseef commented on AMQ-5564:
------------------------------------
So, the anonymous producer is getting created and not removed? Or, that was
the old operation?
It sounds like the right result here is the anonymous producer should get
closed if it was created with session.createProducer(...)- unless there is a
way to create the anonymous producer specifically as a cached producer. The
reasoning is this -- closing an ordinary (i.e. non-pooled) connection removes
producers and consumers created for all sessions in that connection. Some
applications may expect that, so they can bypass the need to do their own
cleanup.
> 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)
