Issue Summary

This is reproducible on Data Center: yes

Steps to Reproduce

1. Set up a two-node instance.
2. Add the secondary TCP connector on node 1. Open JIRA Installation Directory/conf/server.xml in a text editor and add this:

<Connector port="8081"
                   maxThreads="150"
                   minSpareThreads="25"
                   connectionTimeout="20000"
                   enableLookups="false"
                   maxHttpHeaderSize="8192"
                   protocol="HTTP/1.1"
                   useBodyEncodingForURI="true"
                   acceptCount="100"
                   disableUploadTimeout="true"
                   relaxedPathChars="[]|" 
                   relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"/> 

1. Reboot the node 1.
2. Access the node 1 through the secondary TCP connector: http://<node1-ip-address>:<TCP-secondary-port>.
3. Log in and view the dashboard.
4. Then access the same node through the base URL.

Expected Results

The gadget works as expected when accessed through the Jira base URL.

Actual Results

The gadget doesn't load even when accessed through the Jira base URL (see the attached screenshot).

Workaround

• Reboot the impacted node without changing anything in the server.xml file.
• Access the Dashboard via the Base URL for the first time so that the node will set this URL in the cache for the first time.