Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Fri, 8 Dec 2017 08:55:00 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.13123544.1512678497000.416440.1512723300478@Atlassian.JIRA>
In-Reply-To: <JIRA.13123544.1512678497000@Atlassian.JIRA>
References: <JIRA.13123544.1512678497000@Atlassian.JIRA> <JIRA.13123544.1512678497782@jira-lw-us.apache.org>
Subject: [jira] [Commented] (KARAF-5528) Karaf feature deployer should stop
 refreshed bundles together with the updated ones
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 08 Dec 2017 08:55:05 -0000


    [ https://issues.apache.org/jira/browse/KARAF-5528?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1628=
3225#comment-16283225 ]=20

ASF subversion and git services commented on KARAF-5528:
--------------------------------------------------------

Commit 9ee9c891f3486dd69663d11644df1bc3fd345761 in karaf's branch refs/head=
s/master from [~gzres]
[ https://gitbox.apache.org/repos/asf?p=3Dkaraf.git;h=3D9ee9c89 ]

Merge pull request #416 from apache/KARAF-5528

[KARAF-5528] Stop refreshed bundles together with updated and deleted=E2=80=
=A6

> Karaf feature deployer should stop refreshed bundles together with the up=
dated ones
> -------------------------------------------------------------------------=
----------
>
>                 Key: KARAF-5528
>                 URL: https://issues.apache.org/jira/browse/KARAF-5528
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 4.0.10, 4.1.3, 4.2.0.M1
>            Reporter: Grzegorz Grzybek
>            Assignee: Grzegorz Grzybek
>            Priority: Critical
>             Fix For: 4.0.11, 4.1.4, 4.2.0
>
>
> I had a case when features service was provisioned and there were two wir=
ed bundles:
> * bundle A which was updated
> * bundle B which had camel context defined in blueprint, depending on OSG=
i service from bundle A.
> Stopping bundle with came context defined in blueprint, requires access t=
o all {{<reference>}}-d services, otherwise blueprint proxies may wait for =
specific timeout for the services. Having proper start levels set, everythi=
ng works fine.
> But when during deployment, bundle A was updated, it was stopped first. T=
hen, bundle A and B were properly stopped during refresh, but bundle A was =
already stopped (and updated). bundle B hanged during stop.


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