[teiid-issues] [JBoss JIRA] (TEIID-1980) JDBC connection QueryTimeout property appears to be ignored

Tue Mar 27 20:05:47 EDT 2012

    [ https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679823#comment-12679823 ] 

Steven Hawkins commented on TEIID-1980:
---------------------------------------

There are a couple of things here.  Without the fix to TEIID-1883 the timeout value may not be applied correctly.  Also the workaround mentioned for TEIID-1883 is not intended to be a method to set the query timeout, but to increase a lower level timeout that should not actually apply to query timeout.

Also if the same statement is used for additional executions, the timeout defaults to 0 and not the connection property.  I think that we probably should reset to the connection/execution property in that circumstance as well, but that is not a common usecase and probably isn't what is causing an issue.

> JDBC connection QueryTimeout property appears to be ignored
> -----------------------------------------------------------
>
>                 Key: TEIID-1980
>                 URL: https://issues.jboss.org/browse/TEIID-1980
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 7.4
>            Reporter: Paul Nittel
>            Assignee: Johnathon Lee
>
> While testing an EDS patch, I tried to constrain a query by adding ;QueryTimeout=1 to my JDBC connection string. This had no apparent effect. (The query--a repeated UNION ALL of huge tables, followed by a descending ORDER BY--takes over 30 seconds.)
> I also tried 3 and 10 second timeouts, but all allowed the query to continue to completion.

--
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