While deploying new version of the osgi jar, the services/component configurations are bound with the old version of the jar instead of new one.
You see one of the following messages in the log file:
To avoid this issue happening again in your continuous delivery process, the automated deployment script takes care of following things:
If you have any questions or concerns about this issue, join the discussion at the forums Article to address unable to use configuration pid.
When the bundle is first installed the configuration gets bound to the current location. When you update a bundle by uninstalling the old version and then installing the new version, the new install has a new different bundle location and hence the configuration cannot be used.