[ARTEMIS-1304] Communication Timeout on Commit & Failover can lead to message loss

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.2.0
• Assignee: Clebert Suconic
• Reporter: Clebert Suconic
• Created: 25/Jul/17 00:10
• Updated: 03/Aug/21 13:33
• Resolved: 26/Feb/18 17:03

Description

There is a small window that if your server takes more than the call Timeout to activate during a failover, the client will fail to commit with a communication exception, and there won't be any rollbacks associated with the TX.

if the client doesn't treat the exception, the consumers may have a wrong buffer on consumers and you may endup losing messages.

Workaround: always reconnect the session, or rollback after a failure... or set the callTimeout > time your server would need to activate itself.

This is likely a minor issue, but I would rather fix it.

Issue Links

• links to: GitHub Pull Request #1417