[
https://issues.jboss.org/browse/TEIID-1919?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1919:
---------------------------------------
Here is what I've found so far.
We do have an issue with Teiid embedded datasources that are using the calling thread
under a user transaction, the exception there is that the thread is already active under a
transaction. The fix is simple and I'll log a separate jira for that - also you can
workaround by setting useCallingThread=false.
For this issue in my setup I'm using exactly the same Oracle source information, but
in two different datasources. They -ds.xml files are set with:
<no-tx-separate-pools></no-tx-separate-pools>
<track-connection-by-tx></track-connection-by-tx>
<isSameRM-override-value>false</isSameRM-override-value>
I put a simple dynamic vdb on top of those sources. I then modified the teiid and the
non-teiid examples to then issue the same queries - 1 to each source under the user
transaction.
Two reads (as is presumably shown in the teiid procedue) or an insert then read resulted
in no errors.
So we still need to do a little more to narrow this down. I'm using ms_source from
the case, can you provide me via email the other test credentials your using? Then also
we need to repeat the non-teiid test using exactly the same source queries as are produced
by the teiid plan.
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
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1919
URL:
https://issues.jboss.org/browse/TEIID-1919
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7
Environment: Using Oracle XA Datasources
Reporter: Johnathon Lee
Assignee: Steven Hawkins
Attachments: serverExample.log, xasimple.jsp, xatest.jsp
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.
See attached serverExample.log. Error manifests @ 8243.
--
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