- changed status to wontfix
Timesheet plugin error with database connection pool limit
Today our JIRA DC instance became unresponsive because of a database connection pool limit error.
JIRA Version 7.2.9 TSRG Version 30.9
- Sample log: this event happened between midnight to 12:10 EST when this kind of events happened in the past, we need to recycle our servers, so we observed it little bit later and all the nodes were recycled I guess
2017-10-06 18:04:16,334 http-nio-8080-exec-459 WARN Maskuser 1081x3382977x67 1k5lyfm xxxxx..189 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: taken => count=2; marks=[1-0]; pool=60/60 2017-10-06 18:04:16,335 http-nio-8080-exec-459 WARN Maskuser 1081x3382977x67 1k5lyfm xxxxx.189 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: replaced => count=1; marks=[0-0]; pool=59/60 2017-10-06 18:04:16,335 http-nio-8080-exec-459 WARN Maskuser 1081x3382977x67 1k5lyfm xxxxx.189 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: taken => count=2; marks=[1-0]; pool=60/60 2017-10-06 18:04:16,336 http-nio-8080-exec-459 WARN Maskuser 1081x3382977x67 1k5lyfm xxxxx..189 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: replaced => count=1; marks=[0-0]; pool=59/60
2018-01-18 00:09:52,402 http-nio-8080-exec-557 WARN Maskuser 9x3717311x57 1vnr6uw 1xxxxx.244 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: replaced => count=1; marks=[0-0]; pool=57/60 2018-01-18 00:09:52,407 http-nio-8080-exec-557 WARN Maskuser 9x3717311x57 1vnr6uw 1xxxxx..244 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: taken => count=2; marks=[1-0]; pool=58/60 2018-01-18 00:09:52,412 http-nio-8080-exec-557 WARN Maskuser 9x3717311x57 1vnr6uw 1xxxxx..244 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: replaced => count=1; marks=[0-0]; pool=57/60 2018-01-18 00:09:52,412 http-nio-8080-exec-557 WARN Maskuser 9x3717311x57 1vnr6uw xxxxx..244 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: taken => count=2; marks=[1-0]; pool=58/60 2018-01-18 00:09:52,412 http-nio-8080-exec-557 WARN Maskuser 9x3717311x57 1vnr6uw xxxxx..244 /rest/timesheet-gadget/1.0/timesheet.json [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: replaced => count=1; marks=[0-0]; pool=57/60
Comments (5)
-
-
Account Deactivated Hi @V116406 We experienced the same problem today and Atlassian says we should talk to the vendor. Can you share your workaround or solution if you have found one? thanks.
@azhdanov Is there a work around for this problem?
-
-
reporter - edited description
-
reporter - edited description
At this time we have disabled the plugin in our instance.
- Log in to comment
Hi Ioraine,
Unfortunately, I can't do anything in add-on regarding this, because add-on uses Jira API solely, i.e. does not access DB directly. You may see other issue also: https://bitbucket.org/azhdanov/jiratimesheet/issues/1066/timesheet-gadget-slows-down-entire-jira that refers Jira problem, with no much help though.
Also it may be that someone left Jira dashboard opened for some long time unattended, so login session expired and then something goes in Jira that causes this.
Thank you.