Skip to content

bug(db): fixes one leak as seen in the logs#35120

Open
wezell wants to merge 4 commits intomainfrom
issue-35119-db-connection-leaks
Open

bug(db): fixes one leak as seen in the logs#35120
wezell wants to merge 4 commits intomainfrom
issue-35119-db-connection-leaks

Conversation

@wezell
Copy link
Copy Markdown
Member

@wezell wezell commented Mar 25, 2026

ref: #35119

This fixes a leak that is shown 30m after whenever dotCMS starts up.

@github-actions github-actions bot mentioned this pull request Mar 25, 2026
1 task
@github-actions github-actions bot added the Area : Backend PR changes Java/Maven backend code label Mar 25, 2026
@claude
Copy link
Copy Markdown
Contributor

claude bot commented Mar 25, 2026

Claude encountered an error —— View job


Claude encountered an error —— View job


I'll analyze this and get back to you.

wezell and others added 3 commits March 26, 2026 09:17
…g, null guard

- Open one connection outside the loop instead of N+1 connections
- Add per-row try/catch so a bad trigger doesn't abort remaining rows
- Null-check getFireTimeAfter() to avoid NPE on expired cron expressions
- Hoist CronTrigger and updateSql outside the loop

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@wezell
Copy link
Copy Markdown
Member Author

wezell commented Mar 27, 2026

FWIW, this branch already includes 1 round of fixes to appease claude before we ran out of tokens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI: Safe To Rollback Area : Backend PR changes Java/Maven backend code

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant