Bug 1610342

Summary:	[GSS](6.4.z) HORNETQ-1572 Client fail over fails when live shut down too soon
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Matthew Robson <mrobson>
Component:	HornetQ	Assignee:	jboss-set
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Mackay <pmackay>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.4.21	CC:	bmaxwell, csuconic, dcihak, msvehla, rstancel
Target Milestone:	CR1
Target Release:	EAP 6.4.21
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:45:40 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:
Bug Depends On:
Bug Blocks:	1610346, 1567790, 1610355

Description Matthew Robson 2018-07-31 13:00:39 UTC

Description of problem:

In a live-backup scenario, if the live is restarted and shutdown too soon,
the client have a chance to fail on failover because it's internal topology
is inconsistent with the final status. The client keeps connecting to live
already shut down, never trying to connect to the backup.

This fix should go with HORNETQ-1571.


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

How reproducible:
Always

Steps to Reproduce:
1. Failover to backup server
2. Start live server
3. As soon as the live server starts processing messages, kill the live server

Actual results:

Clients will not fail back to the backup, even though failover is successful. They keep trying to connect to the live server which was killed.


Expected results:

Successful failover to the backup

Additional info: