[ARTEMIS-1837] Replication catch up dead locks with clients failing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Assignee: Unassigned
• Reporter: Clebert Suconic
• Created: 30/Apr/18 14:44
• Updated: 17/May/18 02:43
• Resolved: 17/May/18 02:43

Description

if a client failed during the initial replication catch up, the Netty thread would be used to issue an error and reconnect, but the catchup may be waiting completion. Result is a deadlock freezing both backup and live.

Issue Links

• links to: GitHub Pull Request #2052