You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Martyn Taylor (JIRA)" <ji...@apache.org> on 2018/02/26 17:04:06 UTC

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

     [ https://issues.apache.org/jira/browse/ARTEMIS-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martyn Taylor resolved ARTEMIS-1304.
------------------------------------
    Resolution: Fixed

> 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
>            Priority: Major
>             Fix For: 2.2.0, 1.6.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
(v7.6.3#76005)