-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.1.7, 6.2.6, 6.2.7, 6.3.4, 6.3.5, 6.3.6
-
6.01
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
Accessing a user profile, for example https://jira.atlassian.com/secure/ViewProfile.jspa, takes a long period of time to return results. If it consistently causes timeouts the Activity Stream may ban it as a provider, meaning streams may no longer return results for a period of time.
Environment
A larger instance for example 300,000 issues & 1000 projects.
Steps to Reproduce
Browse to a user's profile, for example https://jira.atlassian.com/secure/ViewProfile.jspa.
Expected Results
The results return quickly.
Actual Results
The results take > 10 seconds to return so a timeout is encountered. The below is encountered in atlassian-jira.log:
[atlassian.streams.internal.StreamsCompletionService] Registering failure for stream provider JIRA due to cancellation (timeout)
Timeouts
A timeout is triggered when the activity streams are not returned within the default timeout interval. This can be caused by any of the following:
- The JIRA instance is performing slowly when retrieving results (it may be under load or experiencing a performance problem).
- One of the providers in the stream is responding slowly.
- Something on the network layer is taking a long time.
- The index read speed may be slow (see our Test the Disk Speed KB)
- The provider may not be up and running.
Notes
It is possible for certain Activity Stream providers (Atlassian apps or plugin-specific apps accessible through AppLinks) to be banned from returning results if they consistently time out. This bug fix alleviates some impact of that as it will reduce timeouts on the user profiles within JIRA. If a provider is banned, there is not currently any warning of this - the fix to that is tracked in STRM-2264.
Additionally more information can be found about timeout behaviours in JIRA Activity Stream returns One or more activity sources were slow to respond and are not included.
Workaround
Prior to Activity Streams 5.4.x, it's possible to modify the query string using a front-end proxy such as Apache to rewrite it to be higher. This addresses the symptom rather than the cause (which is the change history results take a long time to return from the database). Add the following to the Apache configuration:
RewriteEngine on
RewriteCond %{REQUEST_URI} ^/plugins/servlet/streams
RewriteCond %{QUERY_STRING} !^timeout.*$
RewriteRule ^(.*)$ %{REQUEST_URI}?timeout=20000&%{QUERY_STRING} [R,L]
If the provider has been banned, and is no longer returning results, either waiting > 24 hours or restarting the instance will address that problem.
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
JRASERVER-32255 Configuration for default timeout in activity stream
- Gathering Interest
-
FUSE-2088 Failed to load
- relates to
-
-
- Closed
-
-
STRM-2140 Loading...
-
- links to
- Testing discovered
-
[JRASERVER-37905] Activity stream in the user profile times out easily on larger instances
Mike Welch
added a comment - Also seeing this on our large instance running 6.3.8 Indeed, please do reach out to us at https://support.atlassian.com so we can help you further Weingarth1370575243.
Thanks 
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Weingarth1370575243: You should contact support rather than commenting on an old closed bug ticket.
Dear Support Team, I´ve change in the system settings the hostname to 443 and now I can´t reach my Jira anymore. Could you tell me how I can change it back. I get a black webpage.
As listed in JIRA Activity Stream returns One or more activity sources were slow to respond and are not included there are multiple causes for timeouts to occur - this issue is one of the possible causes.
If you're on 6.4.1 or higher (which would contain this fix and also JRA-41629) and still experiencing timeouts I'd suggest you raise a support case with us at support.atlassian.com and we can take a further look into the problem. Please include a Support Zip.
this issue still there in 6.4.6 as well..it is not all showing any JIRA info.Its showing the other linked applications like confluence and Bamboo activity.
proposed workaround is not working too good, if filter is applied in activity stream workaround will prevent it from working.
In 6.3.15 the activity stream times out for us all the time - to the point that is will only work for 15 minutes after a restart.
seeing this in our instance and I don't think it's very large... but fisheye seems to perform poorly across the board