[ 
https://issues.apache.org/jira/browse/ARTEMIS-2559?focusedWorklogId=347778&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-347778
 ]

ASF GitHub Bot logged work on ARTEMIS-2559:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Nov/19 22:53
            Start Date: 21/Nov/19 22:53
    Worklog Time Spent: 10m 
      Work Description: asfgit commented on pull request #2899: ARTEMIS-2559 
Connection failure should rollback pending XA TX
URL: https://github.com/apache/activemq-artemis/pull/2899
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 347778)
    Time Spent: 20m  (was: 10m)

> Connection failure should rollback XA transactions if != Prepared
> -----------------------------------------------------------------
>
>                 Key: ARTEMIS-2559
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2559
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.10.1
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Say that your connection failed, and you have a pending XA TX.
> On that state, during a failed connection you should rollback the TX and 
> redeliver messages.
> As a reference to the affected code:
> It should check if failing, the pending TX should be rolled back:
> https://github.com/apache/activemq-artemis/blob/2bf2dba8d3eb346ad4f101ca2b2f1440f72cf3e2/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/ServerSessionImpl.java#L387-L396



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to