You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/02/04 10:37:34 UTC

[jira] [Created] (AMQ-5564) activemq-pool - Either adds new mbeans or add/remove pair of mbean for each producer in use

Claus Ibsen created AMQ-5564:
--------------------------------

             Summary: 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.11.0, 5.10.1
            Reporter: Claus Ibsen


On the AMQ dev mailing list we have talked about a new issue.

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)