[
https://issues.apache.org/jira/browse/AMQ-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-2085.
-------------------------------
Resolution: Not A Problem
The workaround for the JBoss issue is to set findTigerMBeanServer to false.
> AMQ should not install a JMXConnectorServer for an MBeanServer it does not
> create
> ---------------------------------------------------------------------------------
>
> Key: AMQ-2085
> URL: https://issues.apache.org/jira/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.
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
