[ 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 === Resource 2 provides Coordinator Resource1 (xar1::prepare();) // sync 1 Resource2 (ds1::insert(tmLog) ds1::commit() // sync 2) Resource 1 (xar1::commit(); // sync 3) Resource 1 (ds1::delete(tmLog)) ds1::commit() // sync 4 (potentally lazy) XA == Resource 1 (xar1::prepare(); // sync 1) Resource 2 (xar2::prepare(); // sync 2) Coordinator (insert(tmLog) // sync 3) Resource 1 (xar1::commit() // sync 4) Resource 2 (xar2::commit() // sync 5) Coordinator (delete(tmLog) // sync 6 (potentally lazy)) 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 (potentally 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