Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-65

cluster-list shows brokers as master/slave when brokers are not master/slave.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.1
    • 7.0.0
    • None
    • None

    Description

      The doc at http://fuse.fusesource.org/fabric/docs/mq.html says:| "The basic "cluster" of brokers means that you can start multiple unconnected brokers, identified by unique names, in the same group.|

      Each broker will register with that group and clients using discovery:(fabric:<group name>) will naturally load balanced across them."

      However when I created two brokers in a group each with a unique name (using commands below) the "cluster-list" showed the brokers as a master slave configuration. When I connected to the child container and ran a activemq:bstat both brokers appeared to be running. Seems to be an issue with the info displayed from the "cluster-list" command.The broker creation commands:| mq-create --group group_one --create-container g1_instance_1 g1_profile_1|

      mq-create --group group_one --create-container g1_instance_2 g1_profile_2

      The resulting output from cluster-list| ...|

      FuseESB:karaf@root> cluster-list
      [cluster] [id] [master] [services]
      fusemq/group_one g1_profile_2 true tcp://sideshow.home:58813
      fusemq/group_one g1_profile_1 false tcp://sideshow.home:58800
      ...

      Attachments

        Activity

          People

            dejanbosanac Dejan Bosanac
            rhn-support-pfox Patrick Fox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: