[
https://issues.jboss.org/browse/TEIID-2742?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2742:
----------------------------------
Issue Type: Quality Risk (was: Bug)
Priority: Minor (was: Major)
Given the case comments and resolution lessening to a minor quality risk. With the
complexity of the plan (while the error only shows accessing a single table) we can infer
that cursored access is being opened against quite a few tables and in particular causing
a deadlock between processes.
If other workarounds like adjusting the isolation level as suggested in the case (and
http://technet.microsoft.com/en-us/library/ms187373.aspx) do not work and this comes up as
an issue then we'll need to look at it further.
transaction rollback in EDS with SQLServer
------------------------------------------
Key: TEIID-2742
URL:
https://issues.jboss.org/browse/TEIID-2742
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Connector
Affects Versions: 7.7.8
Environment: EDS 5.3.1
Reporter: Hisanobu Okuda
Assignee: Steven Hawkins
Priority: Minor
When using LoadTest within SoapUI, upon increase the number of threads to greater than 1,
we encounter the ATOMIC transaction encountering roll back and the following error is
found. However, when the threads only set to 1, everything works fine.
--
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