Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-67865

Activity Stream is timing out when both comments and history entry number for an issue is too high

XMLWordPrintable

      Summary

      When some issue that is about to appear in Activity Stream gadget has a lot of comments (e.g. 200) made after creation of a lot of history entries (e.g. 15000), the loading time can be too high for the gadget to display the results. The timeout for loading gadget data is unmodifiable and is set at 10 seconds.

      The problem exists because of current way of calculating issue summary for comment is inefficient. It scales defined as number of comments times number of history entries before given comment was made.

      Steps to reproduce

      1. Setup Jira with some issues containing 15000 entries in history tab
      2. Make 200 comments in the issue.
      3. Load Activity Stream gadget

      Or you can use prepared backup for Jira 7.2.15: JRASERVER-67865-reproduction-backup.zip
      (user: admin / password: admin)
      Note: the backup is different than result of steps from above.

      Expected result

      Activity Stream loads with recent comment

      Actual result

      Activity Stream fails to load with message:

      The activity source for 'JIRA' was slow to respond and isn't included.

      Workaround

      If you know which issue is causing the problem you can use Activity Stream gadgets' filters

      Notes

      Activity Stream has safety mechanism that prevents instance from being flooded by Activity Stream calculation. The mechanism will not run the calculation for some time after failure. This backoff time increases with every timeout. For reproduction purposes you can turn off this mechanism by adding JVM property to your Jira: -Dnavlink.failurecache.initialexpiryMs=0.

        1. JRASERVER-67865-reproduction-backup.zip
          1.36 MB

          Form Name

            [JRASERVER-67865] Activity Stream is timing out when both comments and history entry number for an issue is too high

            Issa added a comment -

            It affects 9.12.x versions as well. Please update the bug report. Thx

            Issa added a comment - It affects 9.12.x versions as well. Please update the bug report. Thx

            Rob Ables added a comment -

            We did not have this issue until we moved from mySQL to MSSQL.  This needs to be fixed.  This software is not cheap and bugs like this should not sit on the backlog.  The workaround supplied by support is to have each user put a filter on the activity stream individually?  That's a terrible solution.

            Rob Ables added a comment - We did not have this issue until we moved from mySQL to MSSQL.  This needs to be fixed.  This software is not cheap and bugs like this should not sit on the backlog.  The workaround supplied by support is to have each user put a filter on the activity stream individually?  That's a terrible solution.

            Vicknesh Shanmugam (Inactive) added a comment -

            Hi dkoshel

            I'm one of the Support Engineer from Jira Server team. Our developers keep track of the severity of the bug using the value in "Symptom Severity" field. You may refer to the page below on how we work with the "Symptom Severity" field:

            I can see that the "Symptom Severity" is set to Major hence this bug is being treated as major bug by our developers.

            Hope this explains how we prioritize our bugfixes.

            Best regards,
            Vicknesh
            EMEA Atlassian Support

            Vicknesh Shanmugam (Inactive) added a comment - Hi dkoshel I'm one of the Support Engineer from Jira Server team. Our developers keep track of the severity of the bug using the value in "Symptom Severity" field. You may refer to the page below on how we work with the "Symptom Severity" field: https://www.atlassian.com/blog/announcements/realigning-priority-categorization-public-bug-repository I can see that the "Symptom Severity" is set to Major hence this bug is being treated as major bug by our developers. Hope this explains how we prioritize our bugfixes. Best regards, Vicknesh EMEA Atlassian Support

            Danila Koshel added a comment -

            Hi pdrygas, the issue is still on Low priority and it makes me disappointed. 

            Danila Koshel added a comment - Hi pdrygas , the issue is still on Low priority and it makes me disappointed. 

            Piotr Gąsior added a comment -

             The same problem is in my Jira Core Server 8.0.2 instance ( ~27k issues, 500 projects).

             

             

            Piotr Gąsior added a comment -  The same problem is in my Jira Core Server 8.0.2 instance ( ~27k issues, 500 projects).    

            Pawel Drygas (Inactive) added a comment -

            Hey dkoshel

            I agree that this issue should be considered a 'Major' for that is describes a functionality rendered useless. I am then amending the severity level. Thank you for the notice.

            Cheers,
            Pawel Drygas,
            Jira Server Bugmaster

            Pawel Drygas (Inactive) added a comment - Hey dkoshel I agree that this issue should be considered a 'Major' for that is describes a functionality rendered useless. I am then amending the severity level. Thank you for the notice. Cheers, Pawel Drygas, Jira Server Bugmaster

            Danila Koshel added a comment -

            I really worried about that issue has "Low" priority. The streams brokes each time if there is any "illegal" issue and I'm not sure that my work consists in "checking if activity stream work proper every day because Atlassian can't fix that bug".  pczuj, is there an option to boost this issue? There is not only me who looking/looked "why my activity stream doesn't work" I guess

            Danila Koshel added a comment - I really worried about that issue has "Low" priority. The streams brokes each time if there is any "illegal" issue and I'm not sure that my work consists in "checking if activity stream work proper every day because Atlassian can't fix that bug".  pczuj , is there an option to boost this issue? There is not only me who looking/looked "why my activity stream doesn't work" I guess

              Unassigned Unassigned
              pczuj Przemyslaw Czuj
              Affected customers:
              17 This affects my team
              Watchers:
              35 Start watching this issue

                Created:
                Updated: