[jbossts-issues] [JBoss JIRA] (JBTM-1330) Extend the transaction boundary of a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
Tom Jenkinson (JIRA)
jira-events at lists.jboss.org
Thu Mar 14 12:31:41 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Jenkinson updated JBTM-1330:
--------------------------------
Summary: Extend the transaction boundary of a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources (was: Support Last Logging Resource)
> Extend the transaction boundary of a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1330
> URL: https://issues.jboss.org/browse/JBTM-1330
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
>
> Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
> LLR
> ===
> xar1::prepare(); // sync 1
> ds1::insert(tmLog) ds1::commit() // sync 2
> xar1::commit(); // sync 3
> lazily remove (tmLog) // sync 4
> XA
> ==
> xar1::prepare(); // sync 1
> xar2::prepare(); // sync 2
> tm::log() // sync 3
> xar1::commit() // sync 4
> xar2::commit() // sync 5
> (potentally lazily) remove (tmLog) // sync 6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list