-
Bug
-
Resolution: Done
-
Critical
-
jboss-fuse-6.2.1, jboss-fuse-6.3
-
None
-
%
-
-
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
- duplicates
-
ENTESB-7616 In Red Hat JBoss Fuse 6.3.0 R5, fabric:join leads root container in disconnected state.
- Closed
- is related to
-
ENTESB-6450 fabric-join using external git repo needs a manual intervention
- Closed
- relates to
-
ENTESB-7259 Fabric container tries to create two broker instances
- Closed