AT subordinate implementation leaves window where prepared subordinate TX may be orphaned and not rolled back ------------------------------------------------------------------------------------------------------------- Key: JBTM-646 URL: https://jira.jboss.org/jira/browse/JBTM-646 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6.1.CP03, 4.8.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.9.0, 4.6.1.CP04 The AT subordinate implementation employs a proxy participant registered on behalf of the suibordinate transaction to forward messages from the parent coordinator. There is a window during prepare between completion of the subordinate transaction prepare (which includes logging the subordinate transaction) and logging of the proxy where a crash can occur. When the subordinate transaction is recovered it will wait forever for a message from a non-existent proxy. This can be resolved by ensuring that recovered subordinates and their proxies are reconciled during the first pass of the log. Any transactions whose proxy is not present can be rolled back automatically. This mirrors the way the BA subordinate transaction implementation closes the window. -- 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