mortenstevens commented on issue #13382: URL: https://github.com/apache/cloudstack/issues/13382#issuecomment-4679170800
@shwstppr Switching the connection pool library from HikariCP to DBCP2 did not resolve the problem. Update on the issue: We have performed some additional testing and successfully isolated the conditions under which this connection leak occurs. The Setup: Multiple physical hosts controlled via Dell iDRAC 9 using the Redfish driver. When the global setting outofbandmanagement.background.task.execution.interval was set to 300 seconds (5 minutes), the database connections accumulated indefinitely until the pool was completely exhausted, regardless of the pool backend used. Our Workaround: We found that lowering the execution interval of outofbandmanagement.background.task.execution.interval to 60 seconds mitigates the issue. At this higher frequency, both Java and MySQL inactive sessions are automatically and consistently reaped/evicted shortly after reaching approximately 1000 seconds of idle time. It appears the OOBM background task logic might only trigger proper connection/transaction cleanup routines under high-frequency conditions (like the 60s or lower, while failing to close connections properly when longer intervals are configured. Hope this helps to pinpoint the bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
