karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gareth Collins (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-2367) Config Not Released When Declarative Services Bundle Stopped
Date Sat, 22 Jun 2013 18:12:20 GMT
Gareth Collins created KARAF-2367:
-------------------------------------

             Summary: Config Not Released When Declarative Services Bundle Stopped
                 Key: KARAF-2367
                 URL: https://issues.apache.org/jira/browse/KARAF-2367
             Project: Karaf
          Issue Type: Bug
          Components: karaf-config
    Affects Versions: 2.3.1
            Reporter: Gareth Collins


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)




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message