-
Bug
-
Resolution: Unresolved
-
Medium
-
1
-
Severity 2 - Major
-
1
-
Summary
Bulk rest api calls that fails with DB connection errors is returning a 403 response code to the client.
1. Content response is even more misleading :
<html> <head> <title>Forbidden (403)</title> <!--[if IE]><![endif]--> <script type="text/javascript" >
2. Jira application logs indicates DB connection error from too many request within a short period of time.
ERROR com.atlassian.plugins.rest.common.error.jersey.ThrowableExceptionMapper Uncaught exception thrown by REST service: org.ofbiz.core.entity.GenericDataSourceException: Unable to establish a connection with the database. (PSQL_TOO_MANY_CONNECTIONS Exception already occurred in this workcontext, skipping next getConnection)
Jira is returning wrong response code along with error message. The external App sends API request to Jira and it failed. Jira returns 403 error while it can return 429 error. If the App receives 403, it will stop operation. If the App receives 429, it should retry sending request again.
Steps to Reproduce
- Call REST APIs in continuous succession
Expected Results
If the rate limit is hit, the status 429. Throttling limit state should be returned in headers like here
Actual Results
HTTP 403 response code returned with the following content
<html> <head> <title>Forbidden (403)</title> <!--[if IE]><![endif]--> <script type="text/javascript" >
- is duplicated by
-
JRACLOUD-76290 Calls to Jira Cloud cause 403 Forbidden response
- Closed
- is related to
-
JRACLOUD-70291 500 "FATAL: too many connections for role" caused by Edge malfunction
- Closed
-
JRACLOUD-71874 Report 503 instead of 500 in case of "FATAL: too many connections for role"
- Closed
-
ACJIRA-1913 Loading...
- depended on by
-
DEVHELP-3226 Loading...
-
DEVHELP-3254 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
HOT-94645 Loading...
-
ACJIRA-1929 Loading...