[
https://issues.jboss.org/browse/TEIID-1719?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1719.
-----------------------------------
Assignee: Steven Hawkins
Resolution: Done
The core issue was a missing call in ResultSetImpl to notify the future that it had
received results.
With that fixed and with the new buffering logic a multi-batch test showed that we were
inappropriately sending command complete ahead of all results.
Finally, exceptions were not being propagated to parent futures in the multi-statement
execution patch.
Executing an SQL statement over ODBC interface does not respond
---------------------------------------------------------------
Key: TEIID-1719
URL:
https://issues.jboss.org/browse/TEIID-1719
Project: Teiid
Issue Type: Bug
Components: ODBC
Affects Versions: 7.4.1
Reporter: Pavel Macik
Assignee: Steven Hawkins
Priority: Critical
Fix For: 7.4.1
Attachments: odbc-reproducer.zip, teiid-520ER2.log.zip
When one tries to execute an SQL query using ODBC interface of EDS it the execution get
stuck in the phase of waiting for results from EDS.
An ODBC connection from client is established, a query is sent to EDS, EDS executes the
query against the underlying Oracle DB, EDS receives the response from the DB, but does
not return the response back to the ODBC client...
To reproduce:
1) deploy perf.vdb from resources into SOA-P
2) start SOA-P
3) unzip odbc-reproducer.zip
4) execute clean.sh
5) execute build.sh
6) configure SERVER and ODBC_DRIVER according to your SOA-P and ODBC installation in the
run-test.sh script file
7) execute run-test.sh
Resources (*-ds.xml, *.sql schema and perf.vdb) can be found here
https://svn.devel.redhat.com/repos/jboss-soa/trunk/qa/tests/teargas/perfo...
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira