[
https://issues.jboss.org/browse/TEIID-2394?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2394.
-----------------------------------
Resolution: Done
Promoted the EmbeddedServer thread bound transaction handling to the main
TransactionServerImpl. Also added a check when starting a local transaction to prevent
creating a nested transaction that is not currently handled correctly. This means that
the disableLocalTxn property may still be needed if the client app is starting a local
transaction.
This approach works fine as long as the application code does not do something odd, such
as switching between active transactions in between calls to Teiid.
At some point we'll also want to look into properly supporting subtransactions - both
for client calls and internally for better block transaction semantics.
Allow local connections to use thread bound transactions
--------------------------------------------------------
Key: TEIID-2394
URL:
https://issues.jboss.org/browse/TEIID-2394
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 8.3
To facilitate usage of non-pooled local connections, it would be useful for the engine to
automatically use the thread bound transaction for queries.
An approximate workaround in local mode is to set the userSourceQueryConcurrency to 1 and
use the disableLocalTxn property if needed to prevent calling code from starting a local
transaction. The downside of this approach is that non-transactional work will be
performed serially and Teiid temporary tables will not be transactionally aware.
--
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