[jbossts-issues] [JBoss JIRA] (JBTM-3239) Failing AfterLRA participant calls are not repeated with recovery module

Martin Stefanko (Jira) issues at jboss.org
Wed Jan 8 05:11:12 EST 2020


    [ https://issues.redhat.com/browse/JBTM-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943505#comment-13943505 ] 

Martin Stefanko commented on JBTM-3239:
---------------------------------------

[~tomjenkinson] I updated the title and description. And for the FailingParticipantCallsIT#testFailingAfterLRA you are right. It is not running because it's after TCK. Thanks for the fix.

If there are no objections (even if I would like to wait for [~mmusgrov] opinion which was similar to my proposition) I would start implementing this so we can get TCK and test suite passing as soon as possible.

> Failing AfterLRA participant calls are not repeated with recovery module
> ------------------------------------------------------------------------
>
>                 Key: JBTM-3239
>                 URL: https://issues.redhat.com/browse/JBTM-3239
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.10.1.Final
>            Reporter: Martin Stefanko
>            Assignee: Martin Stefanko
>            Priority: Major
>
> The afterLRA calls are currently delivered only twice when the LRA is finished (twice because of JBTM-3163). When these two calls fail the afterLRA call is never repeated again. However, the specification states that afterLRA must be repeated until the 200 status code is returned.
> The main reason for this issue is the handling of afterLRA listeners in the Transaction object which means that the LRA enters the end phase (Closed/Cancelled) then the afterLRA listeners are called (twice because of above-mentioned issue) but if these calls fail there is nothing telling the transaction object to repeat the calls on the recovery.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jbossts-issues mailing list