Query Execution Was Interrupted Error Code 1317
Contents |
here for a quick overview of the site Help Center Detailed answers to any query execution was interrupted mysql error questions you might have Meta Discuss the workings and policies of
Query Execution Was Interrupted Mysql Sql Developer
this site About Us Learn more about Stack Overflow the company Business Learn more about
Sqlstate 70100 Unknown Error 1317 Query Execution Was Interrupted
hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow
Mysql Execution Time Limit
is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Frequent 'Query execution was interrupted error code 1317' error for select query through elasticsearch java API up vote 0 down vote favorite I understand that there is a question already asked mysql sort aborted query execution was interrupted here about the error 'Query execution was interrupted error code 1317' but I am not sure if my issue and the one discussed in that question are the same. So here's some back ground: I am reading from a MySQL database and pushing the data into elasticsearch database every minute. So I already have one connection open and active to pull the data from MySQL. Now when I am opening another connection for inserting data using Elasticsearch Java API (There are about 49 free connections and I am providing about 3GB RAM for running the Java program which inserts the data), I am constantly getting the interruption exception - [main] 2015-05-12 14:30:41 com.db.exceptions.DBUncategorizedException: DatabaseSourceImplV2:: selectPrepSQLStmt [DATABASE] Query execution was interrupted error code 1317 error state 70100 at com.db.exceptions.SQLExceptionTranslator.translateFromDBErrorStates(SQLExceptionTranslator.java:154) at com.db.exceptions.SQLExceptionTranslator.createDBException(SQLExceptionTranslator.java:85) at com.db.DatabaseSourceImplV2.selectPrepSQLStmt(DatabaseSourceImplV2.java:927) at com.db.DatabaseSourceImplV2.select(DatabaseSourceImplV2.java:556) at com.db.DatabaseSourceImplV2.select(DatabaseSourceImplV2.java:328) at com.es.dao.ArgusESDAO.getF5HttpRequests(ArgusESDAO.java:363) at com.es.F5HttpRequestToES1.pushToES(F5HttpRequestToES1.java:150) at com.es.F5HttpRequestToES1.main(F5HttpRequestToES1.java:93) Caused by: java.sql.SQLException: Query execution was interrupted at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2941) at com.mysql.j
BMO. For more details see Persona Deprecated. Last Comment Bug624791 - Mysql error "Query execution mysql workbench query interrupted was interrupted" should lead to 503+Retry-After Summary: Mysql error "Query execution mysqldump: error 1317: query execution was interrupted when dumping table was interrupted" should lead to 503+Retry-After Status: VERIFIED FIXED Whiteboard: [qa?] Keywords: Product: Cloud Services Classification: Client mysql query timeout Software Component: Server: Sync (show other bugs) Version: unspecified Platform: x86 Mac OS X Importance: -- enhancement (vote) TargetMilestone: --- Assigned To: Ryan Kelly [:rfkelly] QA Contact: TriageOwner: http://stackoverflow.com/questions/30199083/frequent-query-execution-was-interrupted-error-code-1317-error-for-select-quer Mentors: URL: http:// Depends on: 622889 Blocks: 616603 784598 Show dependency tree /graph Reported: 2011-01-11 11:08 PST by Richard Soderberg [:atoll] Modified: 2014-03-14 11:51 PDT (History) CC List: 3 users (show) jbonacci jrgm telliott See Also: Crash Signature: (edit) QA Whiteboard: Iteration: --- Points: --- Tracking Flags: Attachments patch to convert "query interrupted" errors into https://bugzilla.mozilla.org/show_bug.cgi?id=624791 BackendError (3.17 KB, patch) 2012-10-11 15:31 PDT, Ryan Kelly [:rfkelly] telliott: review+ Details | Diff | Splinter Review View All Add an attachment (proposed patch, testcase, etc.) Description Richard Soderberg [:atoll] 2011-01-11 11:08:42 PST If the server code sees the mysql error "Query execution was interrupted", please send 503+Retry-After to the client rather than any other result. That error will only occur when we are killing long-running queries, either by hand or in an automated fashion. This bug is for Python only, y'all may clone for PHP if so desired. Comment 1 Tarek Ziadé (:tarek) 2011-01-11 13:09:09 PST Did you run into this problem ? if yes is there any log or way to reproduce it ? Comment 2 Richard Soderberg [:atoll] 2011-01-21 01:18:50 PST The only way I know to reproduce this problem is to send a really long SELECT to the server and then to go and administratively kill the query. I can work with you further on this to repro from a test PHP
when it starts. The query that returns the data has always executed slowly in my development environment and occassionally the query has reached the default timeout value of 30 seconds before completing. https://corengen.wordpress.com/2009/12/04/mysql-query-fails-with-query-execution-was-interrupted/ I hadn't bothered to add some code override the default value as in the production environment http://www.buzztouch.com/forum/thread.php?tid=784362077DDCDC1D2B1D96D the query executes fairly quickly and is never in danger of timing out. When the query times out the service fails to start. Usually, just starting the service a second time will be successful although I'd sometimes get a second timeout with an appropriate timeout error message in the exception, one further attempt to start the service would succeed. Not today though… And, query execution the error message in the execption looked much more serious: "Query execution was interrupted". After attempting to start the service about five or six times it was clear that it wasn't going to succeed this time. It took a few minutes to realise that this is probably a bug in MySQL. The error always occurred exactly 30 seconds after the call to MySQL to execute the query. So, this almost certainly is a timeout error but the wrong query execution was message is being passed back in the exception. What seems to be happening is that the query times out and MySQL cancels it. The correct error message is passed back to indicate what happened. When the same query is executed again, MySQL is killing the query when the timeout is reached but is appears get confused about why the query is being cancelled. Possibly, because the same query was previously killed, it's deciding that someone has requested the cancellation of the query execution without checking to see that it's actually MySQL's timeout handler that previously cancelled the query and is doing so this time too. Setting an explicit, and longer, timeout value in the Command object's CommandTimeout property fixed the problem. Like this:Like Loading... Related Written by Sea Monkey December 4, 2009 at 1:00 pm Posted in Debugging, Development Tagged with Debugging, Development « Reading values in an XML configuration file from a batchfile. The limits of ServicesPipeTimeout and ServiceBase.RequestAdditionalTime » 4 Responses Subscribe to comments with RSS. Got somehting similar today ( using the dotnet connector / MySql.Data.dll ) It's seems to be a bug in the MySql connector. What threw me off a bit at first was - not only I recieved somewhat misleading exception ( "Sort aborted" / "Query execution interrupted") - as you did - but I did specified a (fairly large) timeout on the connection object. As for yo
AM (4 years ago) Database Error - Query Execution was interrupted Error #1317 I receive the following error in my self hosted control panel (Screens/Actions -> Add New) SELECT P.guid, P.uniquePluginId, P.displayAs, P.category, P.webDirectoryName, P.versionString, P.shortDescription, (SELECT Count(id) AS count FROM bt_items AS I WHERE I.uniquePluginId = P.uniquePluginId AND I.appGuid = 'EA6BB9F9CF89F1359F0116D8C' ) AS countOfScreens FROM bt_plugins AS P LEFT JOIN bt_items AS I ON P.uniquePluginId = I.uniquePluginId GROUP BY P.uniquePluginId ORDER BY countOfScreens DESC ________________________________________ Database Error! Error #:1317 Error: Query execution was interrupted It seems that the bt_screen.php query get interrupted or times out. I checked with my hosting company (Pow Web) and the query time out limit is 60 seconds but I am not sure if that is the issue or if anyone else has seen this issue on their self hosted control panel. I have a lot of records in my bt_items table (11k but from a database record perspective that is not a lot of data. Any ideas or suggestions anyone? Title Comments I receive the following error in my self hosted control panel (Screens/Actions -> Add New) SELECT P.guid, P.uniquePluginId, P.displayAs, P.category, P.webDirectoryName, P.versionString, P.shortDescription, (SELECT Count(id) AS count FROM bt_items AS I WHERE I.uniquePluginId = P.uniquePluginId AND I.appGuid = 'EA6BB9F9CF89F1359F0116D8C' ) AS countOfScreens FROM bt_plugins AS P LEFT JOIN bt_items AS I ON P.uniquePluginId = I.uniquePluginId GROUP BY P.uniquePluginId ORDER BY countOfScreens DESC ________________________________________ Database Error! Error #:1317 Error: Query execution was interrupted It seems that the bt_screen.php query get interrupted or times out. I checked with my hosting company (Pow Web) and the query time out limit is 60 seconds but I am not sure if that is the issue or if anyone else has seen this issue on their self hosted control panel. I have a lot of records in my bt_items table (11k but