Query execution was interrupted

[karthik73]

After the upgrade to Helsinki, users are reporting about the error message " Query execution was interrupted" appearing (during normal list view/submit actions). This appears sporadically, and not for any particular roles/groups/tables.

On checking the logs, this message appears for the insert into syslog or sysevent table, with SQL transient exception. This also appears for the portal page and ui page transactions.

This seems to be associated with some ACL/permission changes in Helsinki, had anyone faced this error during the upgrade? and is there a solution available for this?

[Mwatkins]

"Query execution was interrupted" is a MySQL level error (70100: ER_QUERY_INTERRUPTED). It probably means that a query that was running was killed. This can happen if a transaction is cancelled by a quota, another transaction or a user, but there are a lot of other things that could lead to this error as well. This is probably white noise. Usually if you look in the logs you'll also see that the same session issued a "kill query" operation directly before the query interrupted message. Like this:

2016-09-06 09:47:52 (032) glide.quota.manager SYSTEM Quota exceeded for AMB Transactions, requesting cancel

2016-09-06 09:47:52 (032) glide.quota.manager SYSTEM WARNING *** WARNING *** Transaction: Cancelling   transaction #1353147 receive /amb/rw/default/incident/c3lzX2lkPWJjOWY1MTg0NGZiMWFlMDAwNmM5MDI5ZDAyMTBjN2Q2 (maximum execution time exceeded): Thread AMB-thread-2 (username, 086D288C4F7D6E0006C9029D0210C7AA), after 12063ms

2016-09-06 09:47:52 (034) glide.quota.manager SYSTEM Doing SQLCancel for thread AMB-thread-2

2016-09-06 09:47:52 (034) glide.quota.manager SYSTEM Attempting to cancel MySQL request for transaction [1353147]

2016-09-06 09:47:52 (035) glide.quota.manager SYSTEM Issuing cancel SQL for transaction [1353147]: kill query 483921

2016-09-06 09:47:52 (036) glide.quota.manager SYSTEM Cancelled 0 child transactions

2016-09-06 09:47:52 (040) AMB-thread-2 086D288C4F7D6E0006C9029D0210C7AA WARNING *** WARNING *** Transaction cancelled: maximum execution time exceeded

2016-09-06 09:47:52 (044) AMB-thread-2 086D288C4F7D6E0006C9029D0210C7AA #1353147 receive /amb/rw/default/incident/c3lzX2lkPWJjOWY1MTg0NGZiMWFlMDAwNmM5MDI5ZDAyMTBjN2Q2 -- total transaction time: 0:00:12.075, transaction processing time: 0:00:00.228, total wait time: 0:00:11.847, session wait: 0:00:11.847, semaphore wait: 0:00:00.000, source: , chars: 0, uncompressed chars: 0, SQL time: 72 (count: 8), business rule: 0 (count: 1), phase 1 form length: 0, largest chunk written: 0, request parms size: 0, largest input read: 0

2016-09-06 09:47:52 (046) AMB-thread-4 SYSTEM *** ERROR *** com.glide.db.GlideSQLException: FAILED TRYING TO EXECUTE ON CONNECTION 16:   /* nodeName, gs:086D288C4F7D6E0006C9029D0210C7AA, tx:36916d844fb1ae0006c9029d0210c7e0 */ SELECT sys_cache_flush0.`sequence`, sys_cache_flush0.`sys_id`, sys_cache_flush0.`system_id`, sys_cache_flush0.`catalog`, sys_cache_flush0.`sys_created_on`, sys_cache_flush0.`key`, sys_cache_flush0.`sys_created_by` FROM sys_cache_flush sys_cache_flush0   WHERE sys_cache_flush0.`system_id` != 'appNumber.dcName.service-now.com:node' AND sys_cache_flush0.`sys_created_on` >= '2016-09-06 16:47:08' ORDER BY sys_cache_flush0.`sys_created_on`,sys_cache_flush0.`sequence`

Query execution was interrupted

[pyuen]

Hi Matthew,

Do you mind to show me where did you see this log ? is it from System logs -> transaction log ?

[Mwatkins]

To view these logs you would need to use the Log File Browser or Log File Downloader utility

http://wiki.servicenow.com/index.php?title=Viewing_System_Logs#Logging_Utilities

[tjschmitt]

We've experienced the same problem.in ServiceNow after the upgrade to Helsinki.   It doesn't seem to be tied to any particular event but it is visible in the transaction logs and users are reporting seeing the message appear.