-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
8.22.6, 9.12.7, 9.4.21
-
None
-
8.22
-
6
-
Severity 2 - Major
-
3
-
Steps to reproduce the issue
Data Center: (yes)
- Enabled rate limit.
- Choose Block all requests option.
- Open Version Report gadget and it shows blank screen:
In atlassian-jira.log, we will observe the following errors:
2024-05-15 13:40:02,858+0000 http-nio-8080-exec-21 url: /jira/rest/greenhopper/1.0/xboard/plan/backlog/versions.json; user: admin DEBUG anonymous 820x3449x2 - xxx /rest/greenhopper/1.0/xboard/plan/backlog/versions.json [c.a.r.i.requesthandler.logging.RateLimitedRequestLogger] User [admin] has been rate limited for URL [BASEURL/rest/greenhopper/1.0/xboard/plan/backlog/versions.json] 2024-05-15 13:40:02,863+0000 http-nio-8080-exec-6 url: /jira/plugins/servlet/gadgets/makeRequest; user: admin ERROR admin 820x3448x1 xx xxxx /plugins/servlet/gadgets/makeRequest [o.a.c.c.C.[Catalina].[localhost].[/jira]] Unhandled exception occurred whilst decorating page java.lang.NullPointerException at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher.addResponseToCacheIfSuccessful(HttpClientFetcher.java:102) at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher.performRequest(HttpClientFetcher.java:123) at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher.fetch(HttpClientFetcher.java:73)
Expected Behaviour
The rate limit blocking option should not impact to any Jira internal functionalities.
Actual Behaviour
Version Report gadget was broken after enabled the rate limit functions and set to blocking all external requests.
Workaround
Add the URL below in the com.atlassian.ratelimiting.whitelisted-url-patterns field via Administration > General Configuration > Advanced Settings:
/**/rest/greenhopper/1.0/rapidview,/**/rest/greenhopper/1.0/xboard/config.json,/**/rest/greenhopper/1.0/xboard/plan/backlog/versions.json
Notes
From logs it can be identified that user accessing this gadget got Rate limited. All other gadgets loads successfully. Increasing Rate limit helps issue resolve. Article which describes problem and provides solution is The Version report gadget in the Jira Dashboard is empty . However it could be difficult to analyse logs for customers on their own.
Would it be possible to improve Version Report gadget so that it loads successfully using default rate limit as other gadgets are using ? Probably there might be a need to reduce some HTTP/REST call from gadget or by default increase Requests allowed and Max requests to a higher value.
