[GitHub] [camel] tadayosi commented on pull request #5454: CAMEL-16532: Prevent unregistration of existing endpoints after attem…

[GitBox <gi...@apache.org>]

tadayosi commented on pull request #5454:
URL: https://github.com/apache/camel/pull/5454#issuecomment-825378191


   > New behavior introduced with this change: Dangling mbeans appear when the route startup fails (jira reproducer extended). This is due to the new behavior, that a server.destroy() is only called once the route/server was started
   
   I am not sure if it's acceptable or not. At this moment, it's the choice between the following two:
   - If you try to deploy a duplicate CXF consumer and fail then the existing consumer fails altogether, or
   - If you try to deploy any CXF consumer and immediately fail then you'll see a growing number of dangling MBeans.
   
   Ideally, `doStop()` should look for any other running MBean with the same identity and invoke `destroy()` only if there aren't any.
   
   @davsclaus @oscerd What do you think?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org