Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-3606

Fabric does not recognize master correctly after mq-create with custom parent profile

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jboss-fuse-6.2.1
    • jboss-fuse-6.2
    • Fabric8 v1
    • None
    • % %
    • Hide
      1. start Fuse and create fabric
      2. profile-create --parent mq-base mq-test-base
      3. mq-create --create-container containerA --parent-profile mq-test-base --group groupA brokerA

      Then in cluster list no container is chosen as a master (but actually activemq is running on one of them and the second behaves as slave)

      cluster-list output
      [cluster]                [masters]      [slaves]                            [services]
amq/groupA                                                                            
   brokerA               -              containerA2, containerA             -

      When I use command:
      mq-create --create-container containerB --parent-profile mq-base --group groupB brokerB

      Then fabric correctly chooses master:

      cluster-list output
      [cluster]                [masters]           [slaves]                            [services]
amq/groupB                                                                            
   brokerB               containerB         containerB2                     tcp://dhcp-10-40-2-236.brq.redhat.com:35729, mqtt://dhcp-10-40-2-236.brq.red
hat.com:44114, amqp://dhcp-10-40-2-236.brq.redhat.com:39411, stomp://dhcp-10-40-2-236.brq.redhat.com:43459
      Show
      start Fuse and create fabric profile-create --parent mq-base mq-test-base mq-create --create-container containerA --parent-profile mq-test-base --group groupA brokerA Then in cluster list no container is chosen as a master (but actually activemq is running on one of them and the second behaves as slave) cluster-list output [cluster] [masters] [slaves] [services] amq/groupA brokerA - containerA2, containerA - When I use command: mq-create --create-container containerB --parent-profile mq-base --group groupB brokerB Then fabric correctly chooses master: cluster-list output [cluster] [masters] [slaves] [services] amq/groupB brokerB containerB containerB2 tcp: //dhcp-10-40-2-236.brq.redhat.com:35729, mqtt://dhcp-10-40-2-236.brq.red hat.com:44114, amqp: //dhcp-10-40-2-236.brq.redhat.com:39411, stomp://dhcp-10-40-2-236.brq.redhat.com:43459

      When creating master slave cluster using mq-create command with --parent-profile option using another parent profile than mq-base, then fabric does not recognize master correctly.

            hchirino Hiram Chirino
            knetl.j@gmail.com Jakub Knetl (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: