Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Thu, 19 Sep 2013 08:09:59 +0000 (UTC)
From: =?utf-8?Q?Pablo_Mu=C3=B1iz_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12669232.1379503664202.160759.1379578199818@arcas>
In-Reply-To: <JIRA.12669232.1379503664202@arcas>
References: <JIRA.12669232.1379503664202@arcas>
Subject: [jira] [Commented] (KARAF-2477) Configuration changes not persisted
 to file when cluster:config-propset is executed in a cluster of nodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-2477?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1377=
1684#comment-13771684 ]=20

Pablo Mu=C3=B1iz commented on KARAF-2477:
------------------------------------

Patch for Karaf Cellar trunk.
               =20
> Configuration changes not persisted to file when cluster:config-propset i=
s executed in a cluster of nodes
> -------------------------------------------------------------------------=
--------------------------------
>
>                 Key: KARAF-2477
>                 URL: https://issues.apache.org/jira/browse/KARAF-2477
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-config
>    Affects Versions: cellar-3.0.0
>            Reporter: Pablo Mu=C3=B1iz
>         Attachments: KARAF-2477-cellar-3.0.0.patch
>
>
> Let's suppose a cluster with two nodes: a producer and a consumer, both i=
n default group.
> From producer node _cluster:config-propset_ command is executed to change=
 a property value in _org.apache.karaf.features_ PID.
> Example:
> {code}
> $ cluster:config-propset default org.apache.karaf.features featuresBoot c=
onfig,cellar
> {code}
> _featuresBoot_ value is changed on both nodes, but is not updated on _etc=
/org.apache.karaf.features.cfg_ file.
> In karaf.log file a message like follows is written :
> {code}
> CELLAR CONFIG: retrieved event ClusterConfigurationEvent [type=3D0, id=3D=
org.apache.karaf.features, sourceNode=3DHazelcastNode [id=3Dlocalhost:5701,=
 host=3Dlocalhost, port=3D5701], sourceGroup=3Dorg.apache.karaf.cellar.core=
.Group@5c13d641, destination=3Dnull, force=3Dfalse, postPublish=3Dfalse] wh=
ile groupManager is not available yet
> {code}
> After debugging code I have found that _groupManager_ attribute is not in=
itialized in class _org.apache.karaf.cellar.config.ConfigurationEventHandle=
r_
> _eventHandler_ bean definition in file _config/src/main/resources/OSGI-IN=
F/blueprint/blueprint.xml_ has no dependency injection for _groupManager_.
> Comparing this definition with other branches looks like a regression, be=
cause on branch cellar-2.2.x or cellar-2.3.x this bean definition is
> {code}
> =09    <!-- Cluster Event Handler -->
> =09    <bean id=3D"eventHandler" class=3D"org.apache.karaf.cellar.config.=
ConfigurationEventHandler"
> =09          init-method=3D"init" destroy-method=3D"destroy">
> =09        <property name=3D"clusterManager" ref=3D"clusterManager"/>
> =09        <property name=3D"groupManager" ref=3D"groupManager"/>
> =09        <property name=3D"configurationAdmin" ref=3D"configurationAdmi=
n"/>
> =09        <property name=3D"storage" value=3D"${storage}"/>
> =09    </bean>
> {code}
> Injecting _groupManager_ definition will solve the issue.

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