[teiid-issues] [JBoss JIRA] (TEIID-1919) Teiid exception when XA procedure uses two sources (defined in separate *-ds.xml files) that use different oracle accounts and point at the same oracle instance

[ https://issues.jboss.org/browse/TEIID-1919?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-1919 at 2/1/12 12:40 PM: ---------------------------------------------------------------- However there is another catch, I reopened TEIID-1921 because an additional change was needed. In the embedded scenario, and if not using the calling thread, no transaction actually becomes associated with the work. With that change, the embedded case works with or without useCallingThread set. So this issue remains when using a local socket connection. We need to verify if it only happens with local socket connections vs. remote socket connections. There is likely only a problem in the local case, since the inflow transaction is a new TransactionImple instance that has the same Xid as an existing transaction. We then assume that the new transaction is specifically for use with Teiid - which it may not be since it logically duplicates an existing transaction. I'm not sure if there is a general fix we should attempt (how do we detect if the transaction already existed, do we need to use a different branch id, etc.) since at least in the local case the more appropriate path is to use an embedded datasource connection with the TEIID-1921 fix. was (Author: shawkins): However there is another catch, I reopened TEIID-1921 because an additional change was needed. In the embedded scenario, and if not using the calling thread, no transaction actually becomes associated with the work. With that change, the embedded case works with or without useCallingThread set. So this issue remains when using a local socket connection. However we need to verify if it only happens with local socket connections vs. remote socket connections. There is likely a problem in the local case, since the inflow transaction is a new TransactionImple instance that has the Xid as an existing transaction. We then assume that the new transaction is specifically for use with Teiid - which it may not be since it logically duplicates an existing transaction. I'm not sure if there is a general fix we should attempt (how do we detect if the transaction already existed, do we need to use a different branch id, etc.) since at least in the local case the more appropriate path is to use an embedded datasource connection with the TEIID-1921 fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira