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

[JIRAALIGN-1314] (ERROR 504 Gateway time-out) when attempting to trace an Epic with lots of data associated with it


    • 2
    • Severity 2 - Major
    • A-Team - Usher3

      Issue Summary

      When attempting to trace an epic with a large number of Features, Stories, Tasks, Sprints, PI's, etc. associated with it, the trace will, more often than not, time out with a 504 Gateway Timeout error.

      This is not reproduced on any systems internally, but, customers that have large datasets are encountering this issue.

      Steps to Reproduce

      1. Navigate to the Epics Grid on Jira Align
      2. Find an Epic that has a large amount of data associated with it.
      3. Click on the Epic to bring up the details window.
      4. Click "Trace This Epic" on the right side of the Epic slide-out window

      Expected Results

      The life cylce trace of the epic loads along with all associated data

      Actual Results

      Customer receives a 504 cloudflare error indicating a Gateway timeout

      The below exception is thrown in the Splunk log for this type of situation:

      4:50:51.939 PM	
      { [-]
         ASP_function: Error.asp
         ErrorId: 11741
         PageName: Stories
         correlationid: rh5Nef53mMcya9+zl2z2G/kW/0QvvrDgGw37LSUO4V8=
         customer_db: CustomerTest
         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: /lifecycletrace.asp
         error_line: 0
         error_number: -2147467259
         log_type: exception
         logfrom_location: Website-ASP
         timestamp: 2020-03-24T17:50:51.939000-04:00
         url: https://customertest.agilecraft.com:443/lifecycletrace.asp?PB=epicgrid&Type=1&TO=3407
         urlverb: GET
         user: 4341

      Note - this appears to be a performance defect caused by the amount of data being loaded. Tracing a smaller Epic with less data tied to it does not cause a 504 error.


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

            tdavenport@atlassian.com Tony D.
            kbaxley Kent Baxley
            1 Vote for this issue
            9 Start watching this issue