Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <22701138.68001291295372833.JavaMail.jira@thor>
Date: Thu, 2 Dec 2010 08:09:32 -0500 (EST)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2750) webapp's ActiveMQ JMX MBeans no longer
 available
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dejan Bosanac updated AMQ-2750:
-------------------------------

    Fix Version/s:     (was: 5.4.2)
                   5.5.0

> 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.5.0
>
>
> 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.