[
https://issues.jboss.org/browse/TEIID-1865?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1865.
-----------------------------------
Resolution: Done
Enhanced the multi-threaded consistency of cancel events when reusing a statement - this
was actually causing TestStatement to fail occasionally and switched the connection over
to using a thread safe collection for tracking statements.
Connections are still not thread-safe for examining information outside of a result set,
such as the debug log or annotations, local/global transactions, or manipulating execution
properties through the set statement. All but the transaction logic could be easily
addressed later, but the transaction model of JDBC assumes that the connection represents
a transaction which is not compatible with having thread bound transactions.
Thread-safe JDBC connection
---------------------------
Key: TEIID-1865
URL:
https://issues.jboss.org/browse/TEIID-1865
Project: Teiid
Issue Type: Enhancement
Components: JDBC Driver
Affects Versions: 7.6
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
Fix For: 7.7.1
I would like to share an embedded Teiid JDBC connection across multiple threads without
the JDBC client worrying about synchronization.
For more detail, see forum discussion
http://community.jboss.org/message/641133#641133
--
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