[KARAF-2367] Config Not Released When Declarative Services Bundle Stopped

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.3.1
• Component/s: karaf
• Assignee: Unassigned
• Reporter: Gareth Collins
• Created: 22/Jun/13 18:10
• Updated: 21/Jan/21 15:47

Description

If I have a declarative services bundle which has config associated with it. i.e.:

karaf@root> list -t 0 -s | grep myservice
[ 234] [Active ] [ ] [ 80] com.mycompany.myservice (1.0.0.20130530-jenkins-383)

karaf@root> config:list "(service.pid=com.mycompany.myservice)"
----------------------------------------------------------------
Pid: com.mycompany.myservice
BundleLocation: mvn:com.mycompany/myservice/1.0.0-SNAPSHOT
Properties:
.
.

If I stop or uninstall this bundle, the config does not get released:

karaf@root> stop 234

karaf@root> config:list "(service.pid=com.mycompany.myservice)"
----------------------------------------------------------------
Pid: com.mycompany.myservice
BundleLocation: mvn:com.mycompany/myservice/1.0.0-SNAPSHOT
Properties:
.
.

This is problematic because it stops you from uninstalling the bundle and installing a new bundle at a new location which will reuse the config. To get around this issue I currently must delete the old config and recreate it. This problem persists across karaf restarts.

I know I can also do this:

karaf@root> update 234 <new location>

But that doesn't always work (once I can reproduce this "update" failure consistently, I will open another defect)