activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5564) activemq-pool - Either adds new mbeans or add/remove pair of mbean for each producer in use
Date Wed, 04 Feb 2015 09:38:35 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated AMQ-5564:
-----------------------------
    Attachment: amq-5110.png
                amq-5101.png
                amq-5100.png

Running the camel-example-management with
mvn clean install camel:run

And using different version of ActiveMQ, that is the only change.



> 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
>         Attachments: amq-5100.png, amq-5101.png, amq-5110.png
>
>
> 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)

Mime
View raw message