[jbossts-issues] [JBoss JIRA] (JBTM-3356) Failing AfterLRA calls keep LRA in Closing state
by Martin Stefanko (Jira)
[ https://issues.redhat.com/browse/JBTM-3356?page=com.atlassian.jira.plugin... ]
Martin Stefanko updated JBTM-3356:
----------------------------------
Description:
When the AfterLRA method returns different response codes than 200 the LRA is recovered in the next recovery run in the Closing/Compensating state. The state reported in the AfterLRA is correct (Closed/Canceled) but the status reported by the coordinator at /lra-coordinator is reported as Closing/Canceling which is breaking the LRA status model as the LRA transitions are Active -> Closing -> Closed -> (now the AfterLRA phase starts) -> Closing -> (now the AfterLRA phase finishes) -> Closed.
I wrote a test that reproduces this - [https://github.com/xstefank/narayana/commit/0dd1c6d0671cb2e61697d0907cc2838ec22767a2]
was:When the AfterLRA method returns different response codes than 200 the LRA is recovered in the next recovery run in the Closing/Compensating state. The state reported in the AfterLRA is correct (Closed/Canceled) but the status reported by the coordinator at /lra-coordinator is reported as Closing/Canceling which is breaking the LRA status model as the LRA transitions are Active -> Closing -> Closed -> (now the AfterLRA phase starts) -> Closing -> (now the AfterLRA phase finishes) -> Closed.
> Failing AfterLRA calls keep LRA in Closing state
> ------------------------------------------------
>
> Key: JBTM-3356
> URL: https://issues.redhat.com/browse/JBTM-3356
> Project: JBoss Transaction Manager
> Issue Type: Component Upgrade
> Components: LRA
> Affects Versions: 5.10.4.Final
> Reporter: Martin Stefanko
> Assignee: Martin Stefanko
> Priority: Major
>
> When the AfterLRA method returns different response codes than 200 the LRA is recovered in the next recovery run in the Closing/Compensating state. The state reported in the AfterLRA is correct (Closed/Canceled) but the status reported by the coordinator at /lra-coordinator is reported as Closing/Canceling which is breaking the LRA status model as the LRA transitions are Active -> Closing -> Closed -> (now the AfterLRA phase starts) -> Closing -> (now the AfterLRA phase finishes) -> Closed.
>
> I wrote a test that reproduces this - [https://github.com/xstefank/narayana/commit/0dd1c6d0671cb2e61697d0907cc2838ec22767a2]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)