[CXF-2771] Jetty-HTTP Transport Jetty JMX support causes MBean name collisions

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.7
• Fix Version/s: 2.2.8, 2.3
• Component/s: Transports
• Assignee: David Valeri
• Reporter: David Valeri
• Created: 19/Apr/10 20:34
• Updated: 10/May/10 18:06
• Resolved: 20/Apr/10 15:03

Description

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.