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

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Wed Mar 16 09:46:46 EDT 2011

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

Jonathan Halliday commented on JBTM-443:

working as expected.

LastResourceRecord.doSave is AbstractRecord.doSave i.e. false, so no resource record written for the 1x RR + 1x LRR case

in 2x LLR + 0x RR tx then all records have doSave == false, so no tx log written.

> check LastResource logging and recovery
> ---------------------------------------
>                 Key: JBTM-443
>                 URL: https://issues.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list