On 27 Jan 2009, at 01:07, David Jencks wrote:
I recently started having big problems running AMQ in geronimo -- as
soon as a VM transport connection was started, the jmx connector
stopped working. I eventually discovered this was caused by
activemq registering more JMXConnectorServers whenever
ManagementContext.findMBeanServer is called.
After thinking about this I think the current behavior is
conceptually wrong. I think Activemq should only be creating a
JMXConnectorServer (enabling jmx remoting clients to connect) if
Activemq has itself created the mbean server. If there is already
an mbean server available to use, whoever set it up has presumably
configured it exactly as desired and Activemq shouldn't go around
modifying that configuration.
I've opened AMQ-2085 and modified ManagementContext to avoid this
problem, see rev. 737951.
Note that createMBeanServer still creates the connector as at
present.... only if there is already an mbean server is the behavior
changed.
Any one see a problem with this?
thanks
david jencks
Good idea David!
