[ 
https://issues.apache.org/jira/browse/CAMEL-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725628#comment-16725628
 ] 

Claus Ibsen commented on CAMEL-12980:
-------------------------------------

The problem with using a component name that has not been installed is fine 
IMHO. It allows the bundle to wait a bit for it to be installed and fail after 
the timeout.

Its the other problems that are worse when Camel cannot startup due to an 
exception on startup, which should cause the bundle to be in Failure state and 
not Active as today. 

> Bundle in 'Active' State but Camel Context not initialized
> ----------------------------------------------------------
>
>                 Key: CAMEL-12980
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12980
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint
>    Affects Versions: 2.20.1, 2.21.1
>            Reporter: Xilai Dai
>            Assignee: Grzegorz Grzybek
>            Priority: Critical
>             Fix For: 2.22.3, 3.0.0, 2.24.0, 2.23.1
>
>         Attachments: blueprint.xml
>
>
> The camel context can't get initialized when validation of the 
> RouteDefinition failed (e.g. typo in Uri or add an unsupported option in 
> Uri), but when deploy the blueprint, the CamelContext startup and then 
> shutdown, but the bundle status is still 'Active', only a 
> FailedToCreateRouteException ERROR is logged.
> 318 │ Active  │  80 │ 0.0.0                 │ blueprint.xml
> Attached the simple blueprint.xml for reproduce it.
> The expected behaviour is the bundle is in the 'Failure' status in this case.
> The fix proposal from my side is, move the call of "this.maybeStart()" from 
> blueprintEvent() method to the constructor of the BlueprintCamelContext 
> class. then this kind of Route definition error can be processed during the 
> Blueprint "CREATING" phase. Currently, the start() is invoked after Blueprint 
> in "CREATED" phase. (I tested this fix locally and have the expected 
> 'Failure' bundle status) 
> (This issue is found in Camel 2.20.x, 2.21.x, but it may affects also on 
> master branch)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to