brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoff Macartney (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BROOKLYN-522) When running brooklyn using karaf installing a karaf feature can trigger a brooklyn restrat
Date Thu, 06 Jul 2017 20:11:01 GMT

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

Geoff Macartney resolved BROOKLYN-522.
--------------------------------------
    Resolution: Won't Fix

Cause is Karaf https://github.com/apache/karaf/pull/291, workaround given in comment on this
issue; will go away when we upgrade to Karaf 4.1.1.

> 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)

Mime
View raw message