activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Pickett (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-2750) webapp's ActiveMQ JMX MBeans no longer available
Date Wed, 26 May 2010 13:13:51 GMT
webapp's ActiveMQ JMX MBeans no longer available
------------------------------------------------

                 Key: AMQ-2750
                 URL: https://issues.apache.org/activemq/browse/AMQ-2750
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker, Documentation
    Affects Versions: 5.3.0
            Reporter: Phil Pickett


With ActiveMQ 5.3 and the web demo chat application, I don't see the org.apache.activemq MBeans
in the JBoss jmx-console but with the ActiveMQ 5.2 version I do.

I've bundled up the ActiveMQ demo webapps based on the AMQ version, demo52.war and demo53.war.
 When I deploy the 5.2 version to JBoss, start the chat sample, and enter a username to login,
I see the org.apache.activemq MBeans on the JBoss jmx-console at http://localhost:8280/jmx-console/.
 With the AMQ 5.3 version (and beyond), the org.apache.activemq MBeans are not available on
the JBoss jmx-console.

The behavior I am seeing is due to the change made for AMQ-2085.  The solution is to set the
undocumented ManagementContext property findTigerMbeanServer="false" in the ActiveMQ config.
 I believe the default setting for this property should have been to maintain identical behavior
between AMQ 5.2 and 5.3+.  At a minimum, it seems this property should be documented.




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message