[
https://issues.apache.org/jira/browse/KARAF-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282491#comment-16282491
]
ASF GitHub Bot commented on KARAF-5528:
---------------------------------------
grgrzybek opened a new pull request #416: [KARAF-5528] Stop refreshed bundles
together with updated and deleted…
URL: https://github.com/apache/karaf/pull/416
… ones
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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.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 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)
