Ephemeris Lappis created KARAF-7689:
---------------------------------------
Summary: Blueprint service references not refreshed
Key: KARAF-7689
URL: https://issues.apache.org/jira/browse/KARAF-7689
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.4.3
Reporter: Ephemeris Lappis
Blueprint service references are not always refreshed when the implementing
service is updated : in some cases, references are updated, and any call works,
but in other cases, the client call fails with the following exception :
org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint
container is being or has been destroyed
In our case all is deployed using Karaf features. The service is updated using
two Karaf commands to unistall the old implementation and install the new one :
- feature:repo-remove -u mvn:...
- feature:repo-add -i mvn:...
The service references are all declared with as mandatory by default.
We understand that if an activity leads to call a reference between the two
commands, such an error may occur. Not when the service is available again :
the ls command clearly shows the new service implemented by the new bundle
installed and started by the feature.
It seems that the blueprint doesn't even try to get the new service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
