Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-1281

[JIRAALIGN-1281] (ERROR 504 Gateway time-out) when attempting to search the Administration -> Changes page


    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 10.71
    • 10.66
    • logging
    • 3
    • Severity 2 - Major
    • Avengers - SCORP2

      Issue Summary

      Customer instances with large amounts of data can run into a 504 gateway timeout when trying to search through the Administration -> Changes log. This is due to the search timing out before the Jira Align backend has had a chance to finish processing the search data

      Steps to Reproduce

      1. Log in to Jira Align as a Super Admin
      2. Click Administration in the left navigation menu
      3. Under "Logs" click Changes
      4. Click inside the search box and enter a search term.
      5. Press Enter to initiate the search

      Expected Results

      Search results should be returned

      Actual Results

      The search times out and the customer receives a 504 gateway timeout error.

      The following is seen in the backend logs:

      10:58:50.000 AM	
      2020-03-05 16:58:50 GET /MasterLogs FirstTime=True|-|ASP_0113|Script_timed_out 443 7335 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/80.0.3987.122+Safari/537.36 https://customer.agilecraft.com/ManageExternalTool?FirstTime=True 500 0 121 154783
      host = IP-AC1C052Bindex = mainlinecount = 1source = C:\inetpub\logs\LogFiles\W3SVC6\u_ex200305.logsourcetype = ms:iis:autosplunk_server = idx-i-087f0915f7c4f2825.agilecraft.splunkcloud.com
      10:58:31.105 AM	
      { [-]
         ASP_function: Error.asp
         ErrorId: 19282
         PageName: Changes
         correlationid: 0lLJvpy5IeIH2H8cpfn8qGzZvjQHp7szkigQdOCBRGo=
         customer_db: Customer
         error_aspcode: ASP 0113
         error_aspdescription: The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.
         error_category: Active Server Pages
         error_column: -1
         error_description: Script timed out
         error_file: /MasterLogs.asp
         error_line: 0
         error_number: -2147467259
         log_type: exception
         logfrom_location: Website-ASP
         timestamp: 2020-03-05T11:58:31.105000-05:00
         url: https://customer.agilecraft.com:443/MasterLogs.asp?FirstTime=True
         urlverb: GET
         user: 7335


      Currently there is no known workaround for this behavior. A workaround will be added here when available

            idziadyk@atlassian.com Iryna Dziadyk (Inactive)
            kbaxley Kent Baxley
            1 Vote for this issue
            8 Start watching this issue