Bug 1272517
| Summary: | Cluster topology does not update when using multiple cluster connections | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Amine Belkoura <abelkour> | ||||
| Component: | HornetQ | Assignee: | jboss-set | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Miroslav Novak <mnovak> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.4.2 | CC: | csuconic, msvehla | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-03-01 12:29:02 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
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. |
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: