[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Reopened: (AMQ-2085) AMQ should not install a
From:       "Phil Pickett (JIRA)" <jira () apache ! org>
Date:       2010-04-28 23:56:31
Message-ID: 32877043.7421272498991452.JavaMail.jira () thor
[Download RAW message or body]


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

Phil Pickett reopened AMQ-2085:
-------------------------------


I'm not sure if there is a workaround, but this change appears to have caused the \
issue with org.apache.activemq MBeans no longer appearing in the JBoss jmx-console \
for an app with an embedded broker.  I created a simple jar containing the \
ManagementContext.class with the changes associated with this Jira.  With the AMQ 5.2 \
core jar in the webapp, the MBeans appear in the jmx-console.  When the modified \
version of this class is included in the app, the MBeans no longer appear.


> AMQ should not install a JMXConnectorServer for an MBeanServer it does not create
> ---------------------------------------------------------------------------------
> 
> Key: AMQ-2085
> URL: https://issues.apache.org/activemq/browse/AMQ-2085
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMX
> Affects Versions: 5.3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 5.3.0
> 
> 
> ManagementContext tends to create a JMXConnectorServer whenever findMBeanServer is \
> called.  This seems like really wrong behavior -- amq should not be setting up jmx \
> remoting on mbean servers it hasn't created, certainly not as a side effect of \
> something like creating a vm transport connection:  createConnector():365, \
> ManagementContext.java  findMBeanServer():293, ManagementContext.java
> 	  getMBeanServer():148, ManagementContext.java
> 	  start():77, ManagementContext.java
> 	  start():458, BrokerService.java
> 	  doCompositeConnect():123, VMTransportFactory.java
> 	  doConnect():53, VMTransportFactory.java
> 	  doConnect():51, TransportFactory.java
> 	  connect():80, TransportFactory.java
> 	  createTransport():239, ActiveMQConnectionFactory.java
> 	  createActiveMQConnection():254, ActiveMQConnectionFactory.java
> 	  createConnection():181, ActiveMQConnectionFactory.java
> 	  makeConnection():79, ActiveMQConnectionSupport.java
> 	  makeConnection():61, ActiveMQConnectionSupport.java
> 	  createManagedConnection():169, ActiveMQManagedConnectionFactory.java

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


[prev in list] [next in list] [prev in thread] [next in thread]