-
Bug
-
Resolution: Fixed
-
High
-
13
-
Severity 2 - Major
-
12
-
Summary
Calling search REST API, status 500 FATAL: too many connections for role... was received.
Steps to Reproduce
- Call REST APIs (in this sample Search) 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
See attachment 500_connections (1).txt
- incorporates
-
JRACLOUD-71832 Operations returning "The Jira server could not be contacted..."
- Closed
- is duplicated by
-
JRACLOUD-71836 PSQL exception on third-party addons
- Closed
- relates to
-
JRACLOUD-81846 HTTP Status 403 returned for DB connection error when calling REST APIs
- Gathering Impact
-
DEVHELP-1726 Loading...
-
DEVHELP-2112 Loading...
- was cloned as
-
JRACLOUD-71874 Report 503 instead of 500 in case of "FATAL: too many connections for role"
- Closed
- is related to
-
DEVHELP-1711 Loading...
-
DEVHELP-1730 Loading...
-
DEVHELP-2195 Loading...
-
DEVHELP-2504 Loading...
- resolves
-
JST-417937 Loading...