You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Geoff Macartney (JIRA)" <ji...@apache.org> on 2017/07/06 20:09:00 UTC

[jira] [Commented] (BROOKLYN-522) When running brooklyn using karaf installing a karaf feature can trigger a brooklyn restrat

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

Geoff Macartney commented on BROOKLYN-522:
------------------------------------------

It turns out upon further investigation that this is caused by https://github.com/apache/karaf/pull/291, fixed in Karaf 4.1.1.
Avoiding duplicate bundles in features will avoid the issue until we upgrade to that Karaf.



> When running brooklyn using karaf installing a karaf feature can trigger a brooklyn restrat
> -------------------------------------------------------------------------------------------
>
>                 Key: BROOKLYN-522
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-522
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.10.0, 0.11.0
>            Reporter: Mark McKenna
>            Priority: Minor
>             Fix For: 0.12.0
>
>
> Under certain circumstances installing any karaf feature can trigger a bundle re-wire.
> Prior to 0.12.0 this will cause brooklyn-karaf init to restart shutting down the management context and therefore brooklyn. This required you to restart karaf completly. (Fixed in [#751|https://github.com/apache/brooklyn-server/pull/751])
> h3. Workaround
> When installing a feature use the *-r* flag this informs karaf not to refresh any bundles
> {code}
> feature:install -r my-feature
> {code} 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)