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

Activity Stream can timeout for issues with very long histories

XMLWordPrintable

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

      Summary

      STRM-2272 might cause a timeout with a message saying "The activity source for 'JIRA' was slow to respond and isn't included." and "No activity was found" where the data should be when trying to view Activity Stream gadgets. This issue tracks the upgrade of JIRA to use a more recent version of Activity Streams (5.4.13) in which the issue was fixed.

      Steps to Reproduce

      This issue can be replicated in environments where issues have very long histories and many records are returned.

      Expected Results

      The Activity Stream is expected to show the stream of activities.

      Actual Results

      The Activity Stream shows an error reporting no activities, or the slow to respond message.

      Notes

      For more information, please see: STRM-2272 and JIRA Activity Stream returns One or more activity sources were slow to respond and are not included.

        1. screenshot-1.png
          screenshot-1.png
          61 kB
        2. screenshot-2.png
          screenshot-2.png
          95 kB

            [JRASERVER-41629] Activity Stream can timeout for issues with very long histories

            Vincent Kurutza added a comment -

            https://support.atlassian.com/servicedesk/customer/portal/23/JST-138965

            Thanks.

            Vincent Kurutza added a comment - https://support.atlassian.com/servicedesk/customer/portal/23/JST-138965 Thanks.

            Oswaldo Hernandez (Inactive) added a comment -

            Hi vkurutza1,

            The issue here has been fixed in JIRA 6.4.1 and deployed to Cloud.

            Consequently, If you are facing a problem, could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials should be the same as for this site (https://jira.atlassian.com).

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi vkurutza1 , The issue here has been fixed in JIRA 6.4.1 and deployed to Cloud. Consequently, If you are facing a problem, could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials should be the same as for this site ( https://jira.atlassian.com ). Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Vincent Kurutza added a comment -

            https://ibuildings.jira.com
            This has stopped working once again.
            It was for a time but now all the activity streams are missing the JIRA Stream

            Vincent Kurutza added a comment - https://ibuildings.jira.com This has stopped working once again. It was for a time but now all the activity streams are missing the JIRA Stream

            Oswaldo Hernandez (Inactive) added a comment -

            Hi vkurutza1,

            We currently estimate this to go out to Cloud next week (13 of April 2015). However, please note that this date is only an estimate and might change.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi vkurutza1 , We currently estimate this to go out to Cloud next week (13 of April 2015). However, please note that this date is only an estimate and might change. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Vincent Kurutza added a comment -

            Great news - can I know the release date for 6.5-OD-01?

            Vincent Kurutza added a comment - Great news - can I know the release date for 6.5-OD-01?

            Vincent Kurutza added a comment -

            We are on the Cloud application and still have this issue on the latest release (6.4-OD-15). I was not aware it was also impacting non Cloud users.

            This really should be escalated.

            Vincent Kurutza added a comment - We are on the Cloud application and still have this issue on the latest release (6.4-OD-15). I was not aware it was also impacting non Cloud users. This really should be escalated.

            Andrew Culver added a comment -

            Jon: We found vast improvements in Jira's performance after upgrading to 6.3.13.

            Andrew Culver added a comment - Jon: We found vast improvements in Jira's performance after upgrading to 6.3.13.

            J added a comment -

            We use several issue 10 to 15 unique to log time to. Only a few get into the range mentioned but as soon as I closed those issues and and hid them from the users with permissions, the activity stream showed up. (We lost it at 6.3.8). As soon as the server was under load (mid day or so) activity stream was gone again

            J added a comment - We use several issue 10 to 15 unique to log time to. Only a few get into the range mentioned but as soon as I closed those issues and and hid them from the users with permissions, the activity stream showed up. (We lost it at 6.3.8). As soon as the server was under load (mid day or so) activity stream was gone again

            Steven Ireland added a comment -

            Just to share ... our site recently upgraded to v6.3.15#6346-sha1:dbc023d and started experiencing this time-out issue and we don't have anywhere near the volume mentioned above.

            Steven Ireland added a comment - Just to share ... our site recently upgraded to v6.3.15#6346-sha1:dbc023d and started experiencing this time-out issue and we don't have anywhere near the volume mentioned above.

            Son Tang (Inactive) added a comment -

            We will be upgrading JIRA to a new version of the activity stream plugin which improves the performance of fetching issues with long histories.
            From our testing we have determined that the activity stream can work well with big issues ( > 5000 comments, 5000 worklogs , populated 200 custom field and 300 workflow transition per issue), but we cannot make any guarantee if we have bigger issues.
            There are more performance improvements to be done in this area at a later stage. Please watch this ticket for more information on those https://ecosystem.atlassian.net/browse/STRM-2273
            Regards,
            Son Tang

            Son Tang (Inactive) added a comment - We will be upgrading JIRA to a new version of the activity stream plugin which improves the performance of fetching issues with long histories. From our testing we have determined that the activity stream can work well with big issues ( > 5000 comments, 5000 worklogs , populated 200 custom field and 300 workflow transition per issue), but we cannot make any guarantee if we have bigger issues. There are more performance improvements to be done in this area at a later stage. Please watch this ticket for more information on those https://ecosystem.atlassian.net/browse/STRM-2273 Regards, Son Tang

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              malmeida Marcus Silveira
              Affected customers:
              31 This affects my team
              Watchers:
              61 Start watching this issue

                Created:
                Updated:
                Resolved: