Jetty-HTTP Transport Jetty JMX support causes MBean name collisions
-------------------------------------------------------------------
Key: CXF-2771
URL: https://issues.apache.org/jira/browse/CXF-2771
Project: CXF
Issue Type: Improvement
Components: Transports
Affects Versions: 2.2.7
Reporter: David Valeri
Fix For: 2.3, 2.2.8
When enabling Jetty JMX support by including the Jetty Management classes in
the classpath, CXF creates an MBeanContainer for each Jetty Server it manages.
However, Jetty dynamically creates MBean names for Jetty managed components.
Each MBeanContainer is designed to deal with maintaining unique names, but two
instances of MBeanContainer in the same JVM using the same MBeanServer will
create duplicate names.
This improvement moves the responsibility for maintaining the MBeanContainer to
the JettyHttpServerEngineFactory such that all JettyHttpServerEngine instance
can reference the same MBeanContainer instance. This change removes all
duplicate name warnings except for one. The remaining duplicate name message
is related to Jetty internal logging mechanisms and is outside of the control
of CXF using the current loosely coupled (reflection) approach to working with
the MBeanContainer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
