[
https://issues.apache.org/jira/browse/ARTEMIS-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099323#comment-16099323
]
ASF subversion and git services commented on ARTEMIS-1304:
----------------------------------------------------------
Commit 2a2f25664ca8b1808cc47bf6c42d99585370ea2b in activemq-artemis's branch
refs/heads/1.x from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=2a2f256 ]
ARTEMIS-1304 Message loss on Commmit timeout during failover
(cherry picked from commit 50a900c04b497c470eeb5c69985944cd6666ffa0)
> Communication Timeout on Commit & Failover can lead to message loss
> -------------------------------------------------------------------
>
> Key: ARTEMIS-1304
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1304
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Fix For: 2.2.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
