Details
Critical Description
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 Camel 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.