[teiid-issues] [JBoss JIRA] (TEIID-3024) QueryTimeout not working for synchronous queries against Teiid

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-3024.
-----------------------------------

    Fix Version/s: 8.7.1
                   8.8
       Resolution: Done


Updated the client timeout to be processed for local synch queries.  Also refined the handling of the server side exception produced in the event of a cancel.

> could the local connections be made to work the same way as socked based connections? 

There is a server side timeout that can be set for all queries.  See the query-timeout vdb property - https://docs.jboss.org/author/display/TEIID/VDB+Definition

Otherwise, no this code fix is needed.

> Also does teiid use a localconnection to materialize a view thats marked to be materialized?

I think you are relating this to https://issues.jboss.org/browse/TEIID-3020

Anything specific to materialization should go on that issue.

> QueryTimeout not working for synchronous  queries against Teiid
> ---------------------------------------------------------------
>
>                 Key: TEIID-3024
>                 URL: https://issues.jboss.org/browse/TEIID-3024
>             Project: Teiid
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JDBC Driver
>    Affects Versions: 8.1, 8.7
>            Reporter: gaurav singhal
>            Assignee: Steven Hawkins
>             Fix For: 8.7.1, 8.8
>
>         Attachments: query timeout bug.zip
>
>
> If i run a query with synchronous query with a timeout set using PreparedStatementImpl.setQueryTimeout() method, that timeout is not honored. But if i run the same query with all the same setup and execute the query asynchronously then a timeout happens and warning message like below is printed:
>  
> Jul 02, 2014 10:19:21 AM org.teiid.jdbc.StatementImpl timeoutOccurred
> WARNING: Timeout occurred in Statement.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)