Details
-
Bug
-
Resolution: Fixed
-
Medium
-
5.5.2, 5.5.6, 5.6.3, 5.6.1, 5.5-OD-31
Description
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Note
This error message is the catch-all exception for the JIRA Issues Macro, so there are a number of possible causes for this. The below example is one way of triggering the problem. Another known cause is the response from JIRA taking too long and exceeding the timeouts in Confluence. If you suspect this is the case in your instance, please refer to this KB article for more information.
If you run into this problem, please add the following packages to Confluence Admin > Logging and Profiling and set them to DEBUG level logging:
- com.atlassian.confluence.extra.jira
- com.atlassian.confluence.plugins.JIRA
Having done so, please create a ticket at http://support.atlassian.com/ and attach a Support Zip with this extra logging.
Steps to reproduce
- Add many JIRA issue links on a Confluence page. Try 30.
- Save the page
Expected Results
The JIRA issue links display fine with summary, status, etc.
Actual Results
Confluence displays an error message for each JIRA issue link:
JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
More info
Confluence logs show:
2014-09-03 06:42:40.601459500 2014-09-03 06:42:40,596 ERROR [TP-Processor127] [extra.jira.util.JiraUtil] checkForErrors Received HTTP 413 from server. Error message: Request Entity Too Large 2014-09-03 06:42:40.601462500 -- url: /wiki/display/KEY/My+Page | page: 1234567 | userName: myname | action: viewpage
Attachments
Issue Links
- relates to
-
CONFCLOUD-34793 JIRA Issues Macro returns "Data cannot be retrieved due to an unexpected error"
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...