[jbossts-issues] [JBoss JIRA] Resolved: (JBTM-478) WSAT participant recovery does not reinitiate dispatch of recovered participant messages to coordinator

[Andrew Dinn (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBTM-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Dinn resolved JBTM-478.
------------------------------

    Resolution: Done


Fixed by revision r24886.

This fix also ensures that BA participants resend COMPLETED when they are reinstated i.e. it ensures bottom up BA recovery is initiated.

It also patches another recovery related problem where the isParticipantCompletion field of the BA recovery record was incorrectly initialized when persisting a coordinator completion participant..


> WSAT participant recovery does not reinitiate dispatch of recovered participant messages to coordinator 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-478
>                 URL: https://jira.jboss.org/jira/browse/JBTM-478
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WS-T Implementation
>    Affects Versions: 4.5
>            Reporter: Andrew Dinn
>             Fix For: 4.6
>
>
> When the AT recovery code re-activates a participant after a crash it omits to call recovery() which initiates resend of PREPARED messages to the coordinator. So, recovery only succeeds if it is initiated top-down. This fails if the one phase optimization is employed since the coordinator does not log the transaction after receiving the PREPARED messages (in this case the coordinator would send rollback when it received the PREPARED) . Ditto for two phase if the coordinator crashes before receiving all PREPARED messages.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira