[KARAF-1476] cellar broadcasts configuration changes to a group that has been left before ...

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Cannot Reproduce
• Affects Version/s: cellar-2.2.4
• Fix Version/s: cellar-3.0.0, cellar-2.2.5
• Component/s: cellar
• Assignee: Jean-Baptiste Onofré
• Reporter: Jürgen Kindler
• Created: 14/May/12 14:04
• Updated: 13/Sep/18 13:06
• Resolved: 05/Nov/12 18:10

Description

The scenario is the following:

1. Start up an instance of Karaf
2. Install cellar (using default hazelcast broadcast enabled config)
3. Join a new group
4. Quit the default group
5. Verify that the default group has been left using cluster:group-list ( sometimes, your node will still be in default group even though the quit command gives a different feedback!!! ) - if this fails, quit the default group again, until your node really appears to be out of the default group
6. Start a second instance of Karaf
7. Install cellar (using default hazelcast broadcast enabled config)
8. Verify the configuration of the second container. In my case I realized that there were configurations pushed from the first container to the second, e.g. in Pid: org.ops4j.pax.logging I found paths from the first container inside the configuration of the second container (log4j.appender.sift.appender.file, log4j.appender.out.file)