Query execution was interrupted (max_statement_time exceeded)
Article ID: KB0084084
Updated On:
| Products | Versions |
|---|---|
| Spotfire Server | 7.0 and higher |
Description
When querying data from MySQL, or HeidiSQL, it may work most of the times. Then when you send a larger query, for example an on-demand data table listening to selections on another table in the analysis and getting a large selection, you are presented with an error stating that there has been an internal server error. Looking at the TIBCO Spotfire Server logs shows that you get an error similar to the following:
ERROR 2017-03-24T12:25:58,113+0100 [*pool-5-thread-32, username, #8211, #162829*] ws.dat.AbstractOperator: Start job failed. com.spotfire.ws.dat.OperatorException: com.spotfire.ws.im.IMException: Failed to execute query: Query execution was interrupted (max_statement_time exceeded)Followed by the following in the stack trace:
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLQueryInterruptedException: Query execution was interrupted (max_statement_time exceeded)
Issue/Introduction
When trying to query a MySQL or HeidiSQL data source with a large query, you end up getting the following error instead of the data:
Failed to execute query: Query execution was interrupted (max_statement_time exceeded)
Environment
Connecting to MySQL or HeidiSQL
Resolution
The error that is due to a server side timeout in MySQL/HeidiSQL that was implemented as part of the following:
https://dev.mysql.com/worklog/task/?id=6936
More information on this timeout setting can be found at the following:
https://planet.mysql.com/entry/?id=673840
To resolve this issue, you can reconfigure the timeout in the database. Note that this does not have to be set on the database server level, but can also be set on the user account level.
https://dev.mysql.com/worklog/task/?id=6936
More information on this timeout setting can be found at the following:
https://planet.mysql.com/entry/?id=673840
To resolve this issue, you can reconfigure the timeout in the database. Note that this does not have to be set on the database server level, but can also be set on the user account level.
Additional Information
WL#6936: Implementation of server-side statement timeout - https://dev.mysql.com/worklog/task/?id=6936
Planet MySQL article "Server-side SELECT statement timeouts" - https://planet.mysql.com/entry/?id=673840
Planet MySQL article "Server-side SELECT statement timeouts" - https://planet.mysql.com/entry/?id=673840
Feedback
Yes
No
Powered by
