github-actions[bot] commented on issue #13382: URL: https://github.com/apache/cloudstack/issues/13382#issuecomment-5346145820
## ๐ฏ Triage report The Out-of-Band Management (OOBM) background task appears to leak DB connections (HikariCP or DBCP2) on each execution, eventually exhausting the pool (`db.cloud.maxActive`) and crashing the management server. The reporter and another user independently reproduced growing connection counts tied to OOBM being enabled, and a related discussion (#13542) reports thread dumps after disabling OOBM resolved crashes. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:bug | Confirmed connection-pool exhaustion reproduced by multiple users, independent of pool backend (HikariCP and DBCP2 both affected). | | **Component** | component:management-server, component:database | OOBM background task and DB connection pool management are management-server/database concerns. | | **Severity** | Severity:Major | Leads to full management server outage (SQLTransientConnectionException) once the pool is exhausted; workaround (disable OOBM or shorten interval) exists but core feature becomes unusable at default settings. | | **Labels** | type:bug, component:management-server, component:database, Severity:Major | See above | | **Coding agent** | Needs more info | Root cause (missing `.close()`/connection not released to pool in the OOBM plugin execution path) is suspected but not pinpointed to a specific file/line; needs code-level investigation before a fix can be implemented. | ### ๐ Similar issues - https://github.com/apache/cloudstack/discussions/13542 (related) โ separate report of management server crashes tied to OOBM, resolved by disabling OOBM; includes thread dumps that may help root-cause this. <details><summary>๐ก Notes and suggestions</summary> Confirmed reproduction steps from comments: enable OOBM for hosts, set `outofbandmanagement.background.task.execution.interval` to a longer interval (e.g. 300s), and watch `information_schema.processlist` grow. A maintainer (kiranchavala) already reproduced this. Suggest searching the OOBM background task/driver code for DB connection acquisition that isn't wrapped in try-with-resources or a finally-block release. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/32259459580) ยท sonnet50 262K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) > <details> <summary>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 32259459580, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/32259459580 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- 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]
