[JBoss JIRA] Resolved: (TEIID-1719) Executing an SQL statement over ODBC interface does not respond
by Steven Hawkins (JIRA)
[ 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
14 years, 7 months
[JBoss JIRA] Updated: (TEIID-1719) Executing an SQL statement over ODBC interface does not respond
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1719?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-1719:
----------------------------------
Fix Version/s: 7.5
> 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, 7.5
>
> 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
14 years, 7 months
[JBoss JIRA] Moved: (TEIID-1719) Executing an SQL statement over ODBC interface does not respond
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-1719?page=com.atlassian.jira.plugin... ]
Van Halbert moved SOA-3280 to TEIID-1719:
-----------------------------------------
Project: Teiid (was: JBoss Enterprise SOA Platform)
Key: TEIID-1719 (was: SOA-3280)
Affects Version/s: 7.4.1
(was: 5.2.0.ER2)
(was: 5.2.0.ER3)
Component/s: ODBC
(was: EDS)
Security: (was: Public)
> 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
> Priority: Critical
> 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
14 years, 7 months
[JBoss JIRA] Created: (TEIID-1646) NPE deploying vdb as a data source for Top-Down WSDL test WAR file use
by Paul Nittel (JIRA)
NPE deploying vdb as a data source for Top-Down WSDL test WAR file use
----------------------------------------------------------------------
Key: TEIID-1646
URL: https://issues.jboss.org/browse/TEIID-1646
Project: Teiid
Issue Type: Bug
Affects Versions: 7.5
Environment: 64-bit Fedora, Teiid 7.5 alpha1
Reporter: Paul Nittel
Assignee: Steven Hawkins
I am in the process of executing the E2E Top-Down WSDL test. It calls for using Jopr to create a local tx data source (the VDB) which is then used by the WAR file created during the test. As I saved the DS in Jopr, Jopr reported this error:
Failed to add Resource (see app server log for additional details): java.lang.RuntimeException:Failed to process template. -> java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml DEPLOYMENTS IN ERROR: Deployment "vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml" is in error due to the following reason(s): java.lang.NullPointerException -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml DEPLOYMENTS IN ERROR: Deployment "vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml" is in error due to the following reason(s): java.lang.NullPointerException
I'll be attaching the server log, Designer Model Project Set, and test script.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months