11 a.m.
Paul Nittel created TEIID-1980:
----------------------------------
Summary: 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: Steven Hawkins
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
5:54 a.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1980:
---------------------------------------
Is this specifically against 7.4? Have you tried a post TEIID-1883 client?
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: Steven Hawkins
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
7:14 a.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Paul Nittel commented on TEIID-1980:
------------------------------------
Sorry, Steve, but no. I'm concentrating on the patch at present. I can investigate
this further once that's behind us.
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: Steven Hawkins
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
7:05 p.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
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
7:17 p.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1980:
------------------------------------
If the statement is a prepared statement, would it reset to 0 on subsequent executions?
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
7:52 p.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1980:
---------------------------------------
Yes, PreparedStatements extend Statements. However statement pooling is unnecessary with
Teiid. There's little value in reusing statements.
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
8:35 p.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-1980:
------------------------------------
Does another jira need to be filed in order to get the execution property reused on
subsequent use of the same statement?
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
8:51 p.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1980:
---------------------------------------
If it was not already added, TEIID-1883 should be backported. That will likely resolve
this issue unless statements are being reused. This issue should then be sufficient to
cover that case and whether that should be applied to earlier branches.
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
11:23 a.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1980:
---------------------------------------
I need to amend my comment. The setting to the default timeout only happens after a
timeout, not after each execution. Thus is even less likely to be an issue here.
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
1:57 p.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1980:
---------------------------------------
I did check in the change to ensure that even after timeout the statement will use the
timeout property setting. Can this issue be updated/resolved since the original intent
was likely a dup of TEIID-1883?
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
8:32 a.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Johnathon Lee resolved TEIID-1980.
----------------------------------
Fix Version/s: 7.4.1
Resolution: Duplicate Issue
duplicate of TEIID-1883
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
Fix For: 7.4.1
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
2:42 p.m.
[
https://issues.jboss.org/browse/TEIID-1980?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1980.
---------------------------------
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
Fix For: 7.4.1
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
4309
days inactive
4455
days old
11 comments
4 participants
participants (4)
-
Johnathon Lee (JIRA) -
Paul Nittel (JIRA)
-
Steven Hawkins (JIRA)
-
Van Halbert (JIRA)