activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-2750) webapp's ActiveMQ JMX MBeans no longer available
Date Tue, 21 Feb 2012 20:28:48 GMT

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

Timothy Bish closed AMQ-2750.
-----------------------------

    Resolution: Not A Problem

Solution is to set findTigerMBeanServer to false for the management context, this value is
documented on the ActiveMQ JMX page.
                
> webapp's ActiveMQ JMX MBeans no longer available
> ------------------------------------------------
>
>                 Key: AMQ-2750
>                 URL: https://issues.apache.org/jira/browse/AMQ-2750
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Documentation
>    Affects Versions: 5.3.0
>            Reporter: Phil Pickett
>             Fix For: 5.x
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message