[AMQ-2085] AMQ should not install a JMXConnectorServer for an MBeanServer it does not create

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 5.3.0
• Fix Version/s: 5.3.0
• Component/s: JMX
• Assignee: David Jencks
• Reporter: David Jencks
• Created: 27/Jan/09 00:54
• Updated: 27/Feb/12 21:08
• Resolved: 27/Feb/12 21:08

Description

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