Bug 1272517 - Cluster topology does not update when using multiple cluster connections
Cluster topology does not update when using multiple cluster connections
Status: NEW
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ (Show other bugs)
6.4.2
All All
unspecified Severity high
: ---
: ---
Assigned To: jboss-set
Miroslav Novak
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-16 11:41 EDT by Amine Belkoura
Modified: 2015-10-16 12:05 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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

  None (edit)
Description Amine Belkoura 2015-10-16 11:41:44 EDT
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 12:05:30 EDT
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.