Issue Summary

On pages having multiple Jira issue macro (usually tables) the response time from Jira can be longer than 60 seconds. This is more than the front-end JavaScript configured in Confluence.

Environment

• Confluence v6.12.0
• Jira v8.3.3

Steps to Reproduce

1. Create a page with multiple Jira issue Macros
   • Especially filter which display as tables
   • Data from Jira should be large, so it reaches Confluence after 1 minute
2. Refresh the page in Confluence

Expected Results

Confluence will display the output of all Jira issue macros.

Actual Results

Confluence doesn't display the output for Jira issues which are received by Confluence after 1 minute and shows the following error.

(!) Refresh didn't work. Try again or click an issue to see it in Jira.

Some Jira issues macros will still be displayed, whose data has been received under 1 minute.

Notes

Confluence front-end pulls the data from backend via the following JavaScript (JS)

this.TICK_RETRIES=[0,1*g,1*g,2*g,3*g,5*g,8*g,13*g,13*g,13*g]

This counts to a total of 59 seconds. This means any data received by Confluence after 1 minute of page load will not be displayed.

This issue is different from backend HTTP timeout between Confluence and Jira.

Diagnosis

Confluence sends the following request to check whether Confluence has finished receiving data.

          "url": "<BaseURL>/rest/jiraanywhere/1.0/jira/clientIds/"

This can be seen in HAR file and have two responses:

• 200 --> Means all data has been received
• 202 --> Still receiving

This means that if the last web-request had 202, we will run into this issue.

Workaround

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