[
https://issues.apache.org/jira/browse/ARTEMIS-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099304#comment-16099304
]
ASF GitHub Bot commented on ARTEMIS-1304:
-----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/1417
ARTEMIS-1304 Message loss on Commmit timeout during failover
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-1304
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1417.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1417
----
commit bd7ea4f91883e688817c7c065bd934f956c0026b
Author: Clebert Suconic <[email protected]>
Date: 2017-07-25T00:11:18Z
ARTEMIS-1304 Message loss on Commmit timeout during failover
----
> 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)
