[CAMEL-10914] CxfConsumer doesn't clean up the CXF endpoint MBean upon stop

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.18.2
• Fix Version/s: 2.17.6, 2.18.3, 2.19.0
• Component/s: camel-cxf
• Estimated Complexity: Unknown
• External issue URL: https://issues.jboss.org/browse/ENTESB-6605
• Assignee: Tadayoshi Sato
• Reporter: Tadayoshi Sato
• Created: 01/Mar/17 11:15
• Updated: 20/Apr/21 06:25
• Resolved: 02/Mar/17 08:12

Description

CxfConsumer's doStop() method just does server.stop() and not server.destroy():

    protected void doStop() throws Exception {
        server.stop();
        super.doStop();
    }

This leads to a growing number of dangling endpoint MBeans on CXF side which are never used.

To reproduce the issue, extract the attached reproducer camel-cxf-hawtio.zip and do the following steps:

1. Run the following command:

   $ mvn hawtio:camel
   

2. Access hawtio Camel tab http://localhost:8080/hawtio/. Start and stop the route cxf-greeting several times.
3. Go to hawtio JMX tab and check CXF endpoint MBeans are growing.

Issue Links

• relates to: CAMEL-9502 karaf - Re-installing bundle using camel-cxf throws javax.management.InstanceAlreadyExistsException
• links to: GitHub Pull Request #1498
• links to: GitHub Pull Request #1500