問題

Loading Jira will have the page rendered to users as garbled, gibberish, unreadable text. No errors are thrown in the log, in fact, Jira is seen to be startup and working correctly.

Example of the page rendered by Jira:

診断

Diagnostic Steps

• Performing curl or wget to Jira's dashboard or Jira's REST API returns the correct and readable information 

• Going to $Jira_BASE_URL/plugins/servlet/mobile#myjirahome to render to Jira Mobile View works

• The GZIP Compression in Jira is enabled, can be checked in atlassian-jira.log by searching for jira.option.web.usegzip
• Monitoring tools agent is setup integrated with Jira application. This can be checked in atlassian-jira.log by searching for agentpath setting in JVM parameters

原因

Dynatrace agent script injected to Jira is the cause of the problem. This is due to the Dynatrace XHR monitoring setting is enabled in Dynatrace end.

The following traces are present in Chrome Development Tools's Console log once GZIP compression is disabled in Jira (done through the database):

Uncaught RangeError: Maximum call stack size exceeded
    at String.indexOf (<anonymous>)
    at Object.R [as aIOf] (ruxitagentjs_2SVdfjqrx_10155181109122756.js:98)
    at p (ruxitagentjs_2SVdfjqrx_10155181109122756.js:206)
    at window.require (batch.js?locale=en-US:28)
    at p (ruxitagentjs_2SVdfjqrx_10155181109122756.js:206)
    at window.require (batch.js?locale=en-US:28)
    at p (ruxitagentjs_2SVdfjqrx_10155181109122756.js:206)
    at window.require (batch.js?locale=en-US:28)
    at p (ruxitagentjs_2SVdfjqrx_10155181109122756.js:206)
    at window.require (batch.js?locale=en-US:28)

The ruxitagentjs is what points to the cause being Dynatrace agent.

回避策

Disabling the Dynatrace agent will have Jira to work as normal again.

ソリューション

Disable Dynatrace XHR monitoring setting for the agent connected to Jira application.