Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-577

Throttled execution timed out error when export Audit Log

XMLWordPrintable

    • Severity 1 - Critical
    • 0

      Issue Summary

      When attempting to export the Audit Log for the Automation rule, if the execution takes more than 60 seconds, the operation is throttled to decrease database load. However, once this happens in MSSQL, the query can timeout in an MSSQL server and stay as an idle query indefinitely.

      Steps to Reproduce

      • Create an automation rule which creates a lot of noise in the Automation audit logs, such as introducing a malfunctioning rule that leads to loops;

      Expected Results

      • Audit logs are exported.

      Actual Results

      • The audit log export fails after the method getItemsWithDetailsThrottled is called. The query times out on A4J side but stay as an idle query in the database:
      10.1.51.10 800x42134x1 admin [28/Nov/2022:13:21:05 -0600] "GET /rest/cb-automation/latest/audit/GLOBAL/export/229?&categories=ABORTED&categories=SOME_ERRORS&categories=THROTTLED&dateFrom=2022-11-21&dateTo=2022-11-28 HTTP/1.1" 200 64 60014 "https://localhost/secure/AutomationGlobalAdminAction!iframe.jspa?decorator=none" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36 Edg/107.0.1418.56" "16el3x9"
      • The application log shows the error "Throttled execution timed out"
      2022-11-28 13:19:52,970-0600 https-openssl-nio-443-exec-8 url: /rest/cb-automation/latest/audit/GLOBAL/export/229; user: admin DEBUG admin 798x42131x1 16el3x9 10.1.51.10 /rest/cb-automation/latest/audit/GLOBAL/export/229 [c.c.a.api.util.ExecutionThrottler] Throttled execution timed out.
      
      2022-11-28 13:19:53,141-0600 JIRA-EventThread-8747 DEBUG admin 798x42131x1 16el3x9 10.1.51.10 /rest/cb-automation/latest/audit/GLOBAL/export/229 [c.c.j.p.automation.event.JiraIssueEventListenerImpl] Received generic event :com.atlassian.analytics.api.events.MauEvent@783210b0

      Workaround

      Try reducing the period of the export to as narrow as possible, including reducing the number of actions that you want exported, to reduce the number of items which the query needs to parse. It has been reported by affected customers that this doesn't help in all the cases.

              653c0c4fdc76 Nikhil Patil
              d7087ee2dbf9 Marcos Vinicius
              Votes:
              3 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: