[jbossts-issues] [JBoss JIRA] (JBTM-2356) REST-AT recovery failure

Michael Musgrove (JIRA) issues at jboss.org
Wed Apr 1 12:20:19 EDT 2015


    [ https://issues.jboss.org/browse/JBTM-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055396#comment-13055396 ] 

Michael Musgrove commented on JBTM-2356:
----------------------------------------

Gytis tracked it down.

The bug is in the afterCompletion call where the coordinator does cleanup -  the (rest-at) coordinator maintains an in memory map of active transactions (and a one time read of the recovering transactions from disk at boot time). In this case it should be checking the transaction status before deciding to remove its in-memory copy of the transaction uid.

So when a participant asks for the status the coordinator has no knowledge of it. We didn't spot this in our tests because we only test crash recovery on a single server and in this case on restart the coordinator repopulates its view of recovering transactions.

Gytis has written a 2 server arquillian test to catch these cases in the future.

> REST-AT recovery failure
> ------------------------
>
>                 Key: JBTM-2356
>                 URL: https://issues.jboss.org/browse/JBTM-2356
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 5.0.4
>            Reporter: Michael Musgrove
>            Assignee: Gytis Trikleris
>             Fix For: 5.0.5
>
>
> See linked forum post:
> Start two serves A and B with the coordinator running on A and a participant on server B. Crash server B just before commit. When server B comes back up the coordinator fails to recover the transaction and returns 404 when asked about the transaction.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jbossts-issues mailing list