Bug 1610342 - [GSS](6.4.z) HORNETQ-1572 Client fail over fails when live shut down too soon
Summary: [GSS](6.4.z) HORNETQ-1572 Client fail over fails when live shut down too soon
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.21
Hardware: All
OS: Linux
unspecified
high
Target Milestone: CR1
: EAP 6.4.21
Assignee: jboss-set
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: 1610346 eap6421-payload 1610355
TreeView+ depends on / blocked
 
Reported: 2018-07-31 13:00 UTC by Matthew Robson
Modified: 2021-12-10 16:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:45:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HORNETQ-1572 0 Major Closed Client fail over fails when live shut down too soon 2019-04-17 13:03:08 UTC
Red Hat Issue Tracker JBEAP-15276 0 Major Verified [GSS](7.1.z) ARTEMIS-2041 - Client fail over fails when live shut down too soon 2019-04-17 13:03:08 UTC

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:


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