You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/09/14 07:44:00 UTC

[jira] [Resolved] (CAMEL-16942) Failing blueprint execution displays wrong OSGi status Active

     [ https://issues.apache.org/jira/browse/CAMEL-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-16942.
---------------------------------
    Resolution: Information Provided

Yes Camel 3.11 requires Karaf 4.3, eg the karaf version we test and build with.
Karaf 4.2, is older version of Camel.

> Failing blueprint execution displays wrong OSGi status Active
> -------------------------------------------------------------
>
>                 Key: CAMEL-16942
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16942
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint, karaf, osgi
>    Affects Versions: 3.11.1
>            Reporter: Julien Greffe
>            Priority: Minor
>         Attachments: log.xml
>
>
> Hello,
> when using Karaf 4.2.11 + camel 3.11.1
> and dropping a blueprint which fails, status is {{Active}} whereas it should be {{Failure}}.
> To reproduce:
> - start karaf 4.2.11
> - execute:
> {code}
> karaf@root()> feature:repo-add mvn:org.apache.camel.karaf/apache-camel/3.11.1/xml/features
> karaf@root()> feature:install camel-blueprint
> {code}
> - in {{deploy}} dir, drop {{log.xml}}
> - check logs:
> {code}
> 16:31:34.160 INFO [fileinstall-C:\_PROGRAMS\apache-karaf-4.2.11/deploy] Installing bundle log.xml / 0.0.0
> 16:31:59.985 INFO [fileinstall-C:\_PROGRAMS\apache-karaf-4.2.11/deploy] Karaf BundleStateService not accessible. Bundle state won't reflect Camel context state
> 16:32:00.000 INFO [fileinstall-C:\_PROGRAMS\apache-karaf-4.2.11/deploy] Blueprint bundle log.xml/0.0.0 has been started
> 16:32:00.001 INFO [Blueprint Event Dispatcher: 1] Attempting to start CamelContext: camel-3
> 16:32:00.006 INFO [Blueprint Event Dispatcher: 1] JMX is enabled
> 16:32:00.016 WARN [Blueprint Event Dispatcher: 1] Changing Camel state for bundle 334 to Failure
> 16:32:00.016 ERROR [Blueprint Event Dispatcher: 1] Error occurred during starting CamelContext: camel-3
> org.apache.camel.FailedToCreateRouteException: Failed to create route route3: Route(route3)[From[log://test?fixedRate=true&period=2000] ->... because of Failed to resolve endpoint: log://test?fixedRate=true&period=2000 due to: Failed to resolve endpoint: log://test?fixedRate=true&period=2000 due to: There are 2 parameters that couldn't be set on the endpoint. Check the uri if the parameters are spelt correctly and that they are properties of the endpoint. Unknown parameters=[{fixedRate=true, period=2000}]
> {code}
> Check bundle status:
> {code}
> karaf@root()> list | grep log.xml
> 334 | Active |  80 | 0.0.0   | log.xml
> {code}
> Seems related to this specific log:
> {code}
> 16:31:59.985 INFO [fileinstall-C:\_PROGRAMS\apache-karaf-4.2.11/deploy] Karaf BundleStateService not accessible. Bundle state won't reflect Camel context state
> {code}
> Did we miss something, another feature to install before?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)