[
https://issues.jboss.org/browse/JBTM-1330?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1330:
--------------------------------
Description:
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 5
was:
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 5
Support Last Logging Resource
-----------------------------
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
Priority: Critical
Fix For: 4.17.4, 5.0.0.M3
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 5
--
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