...
A lot of warnings in the logs: Dangerous use of multiple connections
...
| Info |
|---|
Fixed in the 9.0.1 version |
Subversion ALM reuses one Jira database connection pool to run several queries and this is logging a warning, perhaps the overall execution took a while reducing the number of available free connections at the pool. However, none has reported this causes performance issues on any Jira instance.
From Jira 9.0,1 only one query is performed per connection. This takes the connection from the pool for a shorter time.
2020-06-14 13:01:33,619+0200 http-nio-2990-exec-5 WARN admin 781x2920x1 psmhc7 0:0:0:0:0:0:0:1 /projects/DEMO [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: taken => count=3; marks=[2-3]; pool=3/8
java.lang.AssertionError: Explicit stack trace requestedat com.atlassian.jira.util.log.RateLimitingLogger.warnWithTrace(RateLimitingLogger.java:124)
at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor$CountHolder.logWarn(ConnectionPoolHealthSqlInterceptor.java:236)
at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor$CountHolder.taken(ConnectionPoolHealthSqlInterceptor.java:252)
at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor.onConnectionTaken(ConnectionPoolHealthSqlInterceptor.java:89)
at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.lambda$onConnectionTaken$0(ChainedSQLInterceptor.java:64)
at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.forEach(ChainedSQLInterceptor.java:93)
,,,,
...