karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Kindler (JIRA) <j...@apache.org>
Subject [jira] [Created] (KARAF-1476) cellar broadcasts configuration changes to a group that has been left before ...
Date Mon, 14 May 2012 14:05:51 GMT
Jürgen Kindler created KARAF-1476:
-------------------------------------

             Summary: cellar broadcasts configuration changes to a group that has been left
before ...
                 Key: KARAF-1476
                 URL: https://issues.apache.org/jira/browse/KARAF-1476
             Project: Karaf
          Issue Type: Bug
          Components: cellar-core
    Affects Versions: cellar-2.2.4
            Reporter: Jürgen Kindler
            Priority: Critical


The scenario is the following:
# Start up an instance of Karaf
# Install cellar (using default hazelcast broadcast enabled config)
# Join a new group
# Quit the default group
# 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
# Start a second instance of Karaf
# Install cellar (using default hazelcast broadcast enabled config)
# 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)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message