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

Fabric join fails

    XMLWordPrintable

Details

    • % %
    • Hide

      1. Take Fuse 6.2.1 R7 release on 2 nodes
      2. On the 1st node start the fuse and create fabric
      3. On 2nd node join the fabric

      Show
      1. Take Fuse 6.2.1 R7 release on 2 nodes 2. On the 1st node start the fuse and create fabric 3. On 2nd node join the fabric

    Description

      Fabric join command on 6.2.1-186 results in the root container connected status changing to "no" and remains disconnected.

      the node_two does change the connected status from no to yes but the root container remains in "no" status

      JBoss Fuse 6.2.1-186 (R7):

      JBossFuse:karaf@root> container-list 
[id]      [version]  [type]  [connected]  [profiles]              [provision status]
node_two  1.0        karaf   yes          fabric                                    
root*     1.0        karaf   no           fabric                  success           
                                          fabric-ensemble-0000-1

      When we try the same in 6.2.1-084, this behavior is not seen. The root container never goes in the "no" status

      JBoss Fuse 6.2.1-084:

      [id]      [version]  [type]  [connected]  [profiles]              [provision status]
node_two  1.0        karaf   yes          fabric                  success           
root*     1.0        karaf   yes          fabric                  success           
                                          fabric-ensemble-0000-1                    
                                          jboss-fuse-full

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-7616 In Red Hat JBoss Fuse 6.3.0 R5, fabric:join leads root container in disconnected state.

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-6450 fabric-join using external git repo needs a manual intervention

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-7259 Fabric container tries to create two broker instances

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              ggrzybek Grzegorz Grzybek
              rhn-support-hnaram Herambh Naram (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: