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 2012/11/21 22:25:59 UTC

[jira] [Commented] (KARAF-1486) When a new member enters a custom group, it does not install the features that should be installed in that group

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

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

It works for me with Karaf vanilla. Synchronizers are called in the group join.

FYI, since Cellar 2.2.5, you have cluster:sync commands to "force" the call to the synchronizers.
                
> When a new member enters a custom group, it does not install the features that should be installed in that group
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-1486
>                 URL: https://issues.apache.org/jira/browse/KARAF-1486
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-core
>    Affects Versions: cellar-2.2.4
>            Reporter: Jürgen Kindler
>            Assignee: Jean-Baptiste Onofré
>             Fix For: cellar-3.0.0, cellar-2.3.0, cellar-2.2.6
>
>
> I would have expected that on node 3 the feature "guice" would automatically installed as soon as node 3 enters the group hasikasi.
> {panel:title=Node1}
> (1) karaf@trun> cluster:group-list
>    Group                  Members
> * [hasikasi            ] [localhost:5702 localhost:5701* ]
>   [default             ] [localhost:5703 ]
> (4) karaf@trun> features:install guice
> (5) karaf@trun> features:list | grep guice
> [uninstalled] [1.3.2_3        ] jclouds-guice                         jclouds-1.3.2_3             Jclouds - Google Guice
> [installed  ] [3.0            ] guice                                 jclouds-1.3.1               Google Guice
> [uninstalled] [2.9.2          ] camel-guice                           camel-2.9.2                 
> karaf@trun> 
> {panel}
> {panel:title=Node2}
> (2) karaf@trun> cluster:group-list;
>    Group                  Members
> * [hasikasi            ] [localhost:5702* localhost:5701 ]
>   [default             ] [localhost:5703 ]
> (6) karaf@trun> features:list | grep guice
> [uninstalled] [1.3.2_3        ] jclouds-guice                         jclouds-1.3.2_3             Jclouds - Google Guice
> [installed  ] [3.0            ] guice                                 jclouds-1.3.1               Google Guice
> [uninstalled] [2.9.2          ] camel-guice                           camel-2.9.2                 
> karaf@trun> 
> {panel}
> {panel:title=Node3}
> (3) karaf@trun> cluster:group-list
>    Group                  Members
>   [hasikasi            ] [localhost:5702 localhost:5701 ]
> * [default             ] [localhost:5703* ]
> (7) karaf@trun> cluster:group-set hasikasi
>    Group                  Members
> * [hasikasi            ] [localhost:5703* localhost:5702 localhost:5701 ]
>   [default             ] []
> (8) karaf@trun> features:list | grep guice
> [uninstalled] [1.3.2_3        ] jclouds-guice                         jclouds-1.3.2_3             Jclouds - Google Guice
> [uninstalled] [3.0            ] guice                                 jclouds-1.3.1               Google Guice
> [uninstalled] [2.9.2          ] camel-guice                           camel-2.9.2                 
> ((waited a bit) ... 9) karaf@trun> features:list | grep guice
> [uninstalled] [1.3.2_3        ] jclouds-guice                         jclouds-1.3.2_3             Jclouds - Google Guice
> [uninstalled] [3.0            ] guice                                 jclouds-1.3.1               Google Guice
> [uninstalled] [2.9.2          ] camel-guice                           camel-2.9.2                 
> karaf@trun> 
> {panel}

--
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