[CAMEL-12980] Bundle in 'Active' State but Camel Context not initialized

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.20.1, 2.21.1
• Fix Version/s: 2.21.5, 2.22.3, 2.23.1, 2.24.0, 3.0.0
• Component/s: camel-blueprint
• Estimated Complexity: Unknown
• Assignee: Grzegorz Grzybek
• Reporter: Xilai Dai
• Created: 06/Dec/18 07:47
• Updated: 19/Dec/19 17:30
• Resolved: 11/Jan/19 09:53

Description

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)

Issue Links

• is related to: CAMEL-10513 Start BlueprintCamelContext on BlueprintEvent.CREATED