Bug 1272517 - Cluster topology does not update when using multiple cluster connections
Summary: Cluster topology does not update when using multiple cluster connections
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.2
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: ---
Assignee: jboss-set
QA Contact: Miroslav Novak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-16 15:41 UTC by Amine Belkoura
Modified: 2019-03-01 12:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-01 12:29:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
test case configuration file (28.18 KB, application/xml)
2015-10-16 15:41 UTC, Amine Belkoura
no flags Details

Description Amine Belkoura 2015-10-16 15:41:44 UTC
Created attachment 1083735 [details]
test case configuration file

Description of problem:

When setting a cluster with multiple cluster connections, cluster topology does not get updated (except for first cluster connection) when one of the nodes get restarted.

Version-Release number of selected component (if applicable):

6.2 P2

How reproducible:

Reproducible: see below


Steps to Reproduce:

*Use attached  standalone-full-ha.xml: it has two cluster connections, with one queue per cluster connection, and UDP discovery.
* Start server 1
* Start server 2
* Run in server2: "/subsystem=messaging/hornetq-server=default/cluster-connection=my-cluster1:read-attribute(name=topology)": Correct topology
* Run in server2: "/subsystem=messaging/hornetq-server=default/cluster-connection=my-cluster2:read-attribute(name=topology)": Correct topology
* Stop server 1
* Start server 1
* Run in server2: "/subsystem=messaging/hornetq-server=default/cluster-connection=my-cluster1:read-attribute(name=topology)": Correct topology
* Run in server2: "/subsystem=messaging/hornetq-server=default/cluster-connection=my-cluster2:read-attribute(name=topology)":  Topology not correct, server 1 does not connect to cluster

Actual results:

* Cluster view in second server does not get updated for second cluster connection.

Expected results:

* Cluster view in second server should get updated for all cluster connections.

Additional info:

Comment 2 Clebert Suconic 2015-10-16 16:05:30 UTC
You have to specify the cluster connection for the Acceptor, otherwise it will use the first one by default.


Can you please review the configuration and get back to me.


Note You need to log in before you can comment on or make changes to this bug.