[jbossts-issues] [JBoss JIRA] Updated: (JBTM-443) check LastResource logging and recovery

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Tue Oct 19 05:17:55 EDT 2010

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

Jonathan Halliday updated JBTM-443:

    Fix Version/s: 4.15.0

> check LastResource logging and recovery
> ---------------------------------------
>                 Key: JBTM-443
>                 URL: https://jira.jboss.org/browse/JBTM-443
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JTA, JTS, Recovery
>    Affects Versions: 4.4.0.GA
>            Reporter: Jonathan Halliday
>            Assignee: Jonathan Halliday
>             Fix For: 4.15.0
> Where transactions contain LastResource, they may not be fully recoverable. Check if LastResource records are written to the log and if so, what happens to them during recovery.
> Optimise the case where a tx contains multiple last resources, as we need to write a log for such a tx only if it also contains real resources. The case where the tx only has a single resource enlisted is irrelevant as the onePhaseCommit optimization already skips logging.

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


More information about the jbossts-issues mailing list