This issue is related to
Route1 - CXFConsumer with endpoint address /test is already running
Route2 - Gets started with CXFConsumer with same endpoint /test
The expected behavior: Route2 startup fails (endpoint already registered on address). Route1 keeps running.
Expected error on Route2 (endpoint already registered on address):
Due to the change in
CAMEL-10914, server.destroy() will be called after failed startup:
And it will eventually unregister the route:
After failed startup of Route2, Route1 is not registered anymore (HTTP 404 when trying to call /test). I could not reproduce this with embedded Jetty, but we experience this with tomcat on production.
Do you have any suggestion how this could be reproduced in a test using tomcat? Is there a simple way to replace jetty with tomcat?