[
https://issues.apache.org/jira/browse/CAMEL-16532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327092#comment-17327092
]
Manuel Shenavai commented on CAMEL-16532:
-----------------------------------------
[~tadayosi] you are right. The expected behavior is, that Route2 can never be
started and Route1 keeps running.
Current behavior is, that Route1 gets unregistered due to failed startup from
Route2 which then allows Route2 to be started on the second start.
> CXFConsumer unexpectedly unregistered
> -------------------------------------
>
> Key: CAMEL-16532
> URL: https://issues.apache.org/jira/browse/CAMEL-16532
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.24.2, 3.9.0
> Reporter: Manuel Shenavai
> Priority: Minor
>
> This issue is related to CAMEL-10914.
> Desscription:
> 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):
>
> [https://github.com/apache/cxf/blob/master/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/SoapBindingFactory.java#L918]
> Due to the change in CAMEL-10914, server.destroy() will be called after
> failed startup:
>
> [https://github.com/tadayosi/camel/commit/6d31d169dc17138ed02ad1164a4b2209729677fc#diff-174b6ca7cb178d3dc464aa9355d148d95fc0a3ad3f7edb60f0293fac988d3e05R100]
> And it will eventually unregister the route:
>
> [https://github.com/apache/cxf/blob/master/core/src/main/java/org/apache/cxf/endpoint/ServerImpl.java#L191]
> Observed behavior:
> 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?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
