Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-32525

Pages/Blogs timeout if they contain too many JIRA Issues Macros

XMLWordPrintable

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      When a page/blog has too many JIRA Issues Macros, the page times out as Confluence tries to make JIRA calls for all the macros.

      The correct behaviour should be to call JIRA asynchronously and timeout the individual macros, not the page.

      The number of calls that JIRA can handle should also be considered. We should avoid overloading JIRA.

      Workaround:

      Split out the JIRA Issues Macro onto separate pages.

      Also avoid using functionality that avoids loading multiple pages at once, such as viewing the blogs posts of a space, as this will trigger many calls to JIRA simultaneously.

      Fix

      Upgrade to JIRA Macros version 5.5.4. This was bundled in Confluence 5.5.

      Important note:

      This fix makes use of JIRA request batching which is only available since JIRA 6.0.29. For the older version of JIRA (5+), this fix has no effect.

            [CONFSERVER-32525] Pages/Blogs timeout if they contain too many JIRA Issues Macros

            Stefan Hett added a comment -

            @collab-admin Given the other comments above I assume this is a typo and should rather say: JIRA 6.0.2+.

            Stefan Hett added a comment - @collab-admin Given the other comments above I assume this is a typo and should rather say: JIRA 6.0.2+.

            collab-admin@lge.com added a comment -

            how can i get the the JIRA 6.0.29?
            There is not the JIRA 6.0.29 in JIRA release note.

            collab-admin@lge.com added a comment - how can i get the the JIRA 6.0.29? There is not the JIRA 6.0.29 in JIRA release note.

            Nguyen Dang added a comment -

            Hi sgoldberg, unfortunately this only fixes the problem for JIRA 6.0.29+. You can try increasing the size of background worker for JIRA Macro by specifying jira.executor.threadpool.size environment variable, the default value is 4.

            Nguyen Dang added a comment - Hi sgoldberg , unfortunately this only fixes the problem for JIRA 6.0.29+. You can try increasing the size of background worker for JIRA Macro by specifying jira.executor.threadpool.size environment variable, the default value is 4.

            Steve Goldberg added a comment -

            Hi,

            I believe we are experiencing the issue described here. We are using Confluence 5.5.1 and JIRA 5.2.11. We've upgraded to the latest version of this macro but are still experiencing the issue. Can I confirm that this upgrade only fixes the problem for 6.0.2 and above? If so, is there anything I can do for our services other than upgrade (we have issues surrounding other plugins that would make it difficult).

            Thanks,

            Steve

            Steve Goldberg added a comment - Hi, I believe we are experiencing the issue described here. We are using Confluence 5.5.1 and JIRA 5.2.11. We've upgraded to the latest version of this macro but are still experiencing the issue. Can I confirm that this upgrade only fixes the problem for 6.0.2 and above? If so, is there anything I can do for our services other than upgrade (we have issues surrounding other plugins that would make it difficult). Thanks, Steve

            Anatoli added a comment -

            Yes, the fix is already installed in odemand. If you still have issues, can you please create a support ticket and we will help you out.

            Anatoli added a comment - Yes, the fix is already installed in odemand. If you still have issues, can you please create a support ticket and we will help you out.

            Christoph Diefenthal added a comment -

            akazatchkov thank you - does that mean, that the bugfix is already installed in ondemand (because we still have issues), or does it come with https://confluence.atlassian.com/display/AOD/2014/06/03/2nd+of+June+completed+Atlassian+OnDemand+upgrade ?

            Christoph Diefenthal added a comment - akazatchkov thank you - does that mean, that the bugfix is already installed in ondemand (because we still have issues), or does it come with https://confluence.atlassian.com/display/AOD/2014/06/03/2nd+of+June+completed+Atlassian+OnDemand+upgrade ?

            Anatoli added a comment -

            Hi Cristoph, Yes the fix has already been delivered to OnDemand.

            Anatoli added a comment - Hi Cristoph, Yes the fix has already been delivered to OnDemand.

            Christoph Diefenthal added a comment -

            Hi everybody,

            is the bugfix included in https://confluence.atlassian.com/display/AOD/2014/06/03/2nd+of+June+completed+Atlassian+OnDemand+upgrade ?

            Christoph Diefenthal added a comment - Hi everybody, is the bugfix included in https://confluence.atlassian.com/display/AOD/2014/06/03/2nd+of+June+completed+Atlassian+OnDemand+upgrade ?

            saravanan subramanian added a comment -

            Thanks for your help

            saravanan subramanian added a comment - Thanks for your help

            Nguyen Dang added a comment -

            saravanan.subramanian, it was fixed in the 5.5.4 version of the plugin.

            Nguyen Dang added a comment - saravanan.subramanian , it was fixed in the 5.5.4 version of the plugin.

              ttranminh Tam Tran
              rbattaglin Renan Battaglin
              Affected customers:
              13 This affects my team
              Watchers:
              38 Start watching this issue

                Created:
                Updated:
                Resolved: