You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2013/10/03 15:24:42 UTC

[jira] [Commented] (KARAF-2477) Configuration changes not persisted to file when cluster:config-propset is executed in a cluster of nodes

    [ https://issues.apache.org/jira/browse/KARAF-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785075#comment-13785075 ] 

Jean-Baptiste Onofré commented on KARAF-2477:
---------------------------------------------

Fixed on Cellar trunk: http://svn.apache.org/viewvc?view=revision&revision=1528846

> Configuration changes not persisted to file when cluster:config-propset is 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ñiz
>            Assignee: Jean-Baptiste Onofré
>             Fix For: cellar-3.0.0
>
>         Attachments: KARAF-2477-cellar-3.0.0.patch
>
>
> Let's suppose a cluster with two nodes: a producer and a consumer, both in 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 config,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=0, id=org.apache.karaf.features, sourceNode=HazelcastNode [id=localhost:5701, host=localhost, port=5701], sourceGroup=org.apache.karaf.cellar.core.Group@5c13d641, destination=null, force=false, postPublish=false] while groupManager is not available yet
> {code}
> After debugging code I have found that _groupManager_ attribute is not initialized in class _org.apache.karaf.cellar.config.ConfigurationEventHandler_
> _eventHandler_ bean definition in file _config/src/main/resources/OSGI-INF/blueprint/blueprint.xml_ has no dependency injection for _groupManager_.
> Comparing this definition with other branches looks like a regression, because on branch cellar-2.2.x or cellar-2.3.x this bean definition is
> {code}
> 	    <!-- Cluster Event Handler -->
> 	    <bean id="eventHandler" class="org.apache.karaf.cellar.config.ConfigurationEventHandler"
> 	          init-method="init" destroy-method="destroy">
> 	        <property name="clusterManager" ref="clusterManager"/>
> 	        <property name="groupManager" ref="groupManager"/>
> 	        <property name="configurationAdmin" ref="configurationAdmin"/>
> 	        <property name="storage" value="${storage}"/>
> 	    </bean>
> {code}
> Injecting _groupManager_ definition will solve the issue.



--
This message was sent by Atlassian JIRA
(v6.1#6144)