-
Bug
-
Resolution: Not a bug
-
High
-
17
-
Severity 3 - Minor
-
13
-
Summary
In certain conditions, the underlying functions required for the `rest/api/2/search` to complete will time out.
When that happens the response code is a 500 with Internal Server Error as message.
Steps to Reproduce
This can usually be reproduced in significantly big sites.
Expected Results
The request returns a status code corresponding to a timeout (for example a 408).
Actual Results
The request returns a 500 status code with Internal Server Error as message.
Notes
Known conditions leading to this:
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-76460 JQL search against a large number of entity properties results in timeout errors
- Closed
-
JRACLOUD-71874 Report 503 instead of 500 in case of "FATAL: too many connections for role"
- Closed