karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Grzybek (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-5528) Karaf feature deployer should stop refreshed bundles together with the updated ones
Date Thu, 07 Dec 2017 20:29:00 GMT
Grzegorz Grzybek created KARAF-5528:
---------------------------------------

             Summary: Karaf feature deployer should stop refreshed bundles together with the
updated ones
                 Key: KARAF-5528
                 URL: https://issues.apache.org/jira/browse/KARAF-5528
             Project: Karaf
          Issue Type: Bug
          Components: karaf-feature
    Affects Versions: 4.2.0.M1, 4.1.3, 4.0.10
            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 wired bundles:
* bundle A which was updated
* bundle B which had camel context defined in blueprint, depending on OSGi service from bundle
A.

Stopping bundle with came context defined in blueprint, requires access to all {{<reference>}}-d
services, otherwise blueprint proxies may wait for specific timeout for the services. Having
proper start levels set, everything works fine.

But when during deployment, bundle A was updated, it was stopped first. Then, 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)

Mime
View raw message