...
This causes the available db connection pool to get exhausted and is causing the entire Jira instance to crash.
Workaround
Please consider using Time Reports for Jira Server instead, it has quite same UI, but different backend, so it does not have such problems. See also Comparison Matrix for feature differences.
Solution
Unfortunately, this problem has no clear solution, please contact Atlassian Support for help.Note, stopping however Atlassian has confirmed a bug, see JRASERVER-45794 for workaround suggested by Atlassian.
Otherwise, it may be that problem happens due to dashboard left unattended, when session expires. You may try to remove all add-on gadgets from all dashboards, if it's acceptable. See https://bitbucket.org/tempo-io/servertimesheet/wiki/Usage_Trackingfor how to find them.
Stopping JIRA service, rebooting the DB server, then starting JIRA service might help.
See also issue#1066 and contact Atlassian Support for help.
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...