Performance Issue causing Blank white dashboards and prime Timesheets requests timeouts


This post will serve as a guideline as to how to find this issue and how to proceed with it.


There is a known bug currently happening on Timesheet Reports and Gadgets for Jira Server and for Jira Data Center, that causes the slowness and eventually crashes the instance. It’s still unknown as to what triggers this bug to happen, most cases happens when the user instance reaches a threshold of issues and worklogs, other users are stating that this bug started happening after an upgrade on Jira or the Timesheet Reports and Gadgets.

When analyzing a Support Zip from a instance with this bug in effect, you may find a huge amount of the WARN message

1 2018-04-26 11:19:10,495 http-nio-8080-exec-6 WARN <username> 679x59888x11 fnw9cw /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: replaced => count=0; marks=[-1-0]; pool=6/20

This causes the available db connection pool to get exhausted and is causing the entire Jira instance to crash.

Its also possible that you may not find any messages regarding this issue on your instance logs, but generating a Har file you will find that the requests from the Timesheet plugin are returning 0, or taking more than 10 min to load.

All this options are related to the Performance Issue causing Blank white dashboards and prime Timesheets requests timeouts.


We are currently working to solve this bug, but unfortunately we do not have an ETA as to when this bug will be fixed, in the meantime, here are some steps you can do to solve this issue as a workaround:

  • Stop JIRA service;

    Reboot the DB Server;

    Start JIRA Service again;

    If its possible, uninstall the plugin (as all data is stored natively within Jira no worklog data or Dashboard report will be lost by uninstalling the plugin;

  • Clear the plugin cache from Jira Home, to better understand how to do this please perform the following:

    • Shut down JIRA

    • Delete the following hidden plugin cache directories:

      • JIRA_HOME/plugins/.bundled-plugins


    • Restart JIRA (These directories will be recreated on JIRA reboot with new plugin cache)

  • Install it again

If this Does not Solve your issue, one other option is to use instead Time Reports for Jira Server/Data Center, that offers the same, if not more flexible ways to generate time tracking reports, you can see this documentation   for more information. Since it uses a different set of codes on the backend, we have confirmed that this bug does not affect the Time Reports plugin.

Since Both Timesheet Reports and Gadgets and Time Reports plugins mainly reads the information from Jira Database, like Time Tracking data, no data will be lost changing from one plugin to another, but you would have to manually create new gadgets and reports.


As soon as we have more information regarding this bug we will update on this post as well.