Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Priority: High
Component/s: Ecosystem
Labels:

Support reference count:
13
Symptom Severity:
Severity 2 - Major
UIS:
12
Bug Fix Policy:
View Atlassian Cloud bug fix policy

Description

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

Attachments

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

500_connections (1).txt
32 kB
20/Sep/2018 5:45 AM
image-2019-04-09-07-28-49-915.png
210 kB
09/Apr/2019 2:28 PM
issue-duration.png
213 kB
04/Apr/2019 9:59 PM
issue-duration-95.png
173 kB
03/Apr/2019 9:18 PM

Issue Links

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 cloned by: JCES-670 Loading...; JCES-697 Loading...

is related to: DEVHELP-1711 Loading...; DEVHELP-1730 Loading...; DEVHELP-2195 Loading...; DEVHELP-2504 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...

resolves: JST-417937 Loading...

(1 was cloned as, 2 is cloned by, 4 is related to, 3 mentioned in, 1 resolves)

Activity

People

Assignee:: Nicolas Meessen

Reporter:: Bartłomiej Jańczak [SoftwarePlant]

Votes:: 26 Vote for this issue

Watchers:: 42 Start watching this issue

Dates

Created:: 20/Sep/2018 5:41 AM

Updated:: 05/Jul/2023 4:06 PM

Resolved:: 16/Apr/2019 12:07 AM