-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: Job Processing Loop Fails Due to Database Connection Timeout #30668
Comments
github-project-automation
bot
moved this from In Review
to Internal QA
in dotCMS - Product Planning
Nov 21, 2024
github-project-automation
bot
moved this from Internal QA
to Current Sprint Backlog
in dotCMS - Product Planning
Nov 21, 2024
jgambarios
moved this from Current Sprint Backlog
to Internal QA
in dotCMS - Product Planning
Nov 21, 2024
After testing the jobs queue over the past few days, I can confirm that the connection issue has not reoccurred. |
fabrizzio-dotCMS
moved this from Internal QA
to QA - Backlog
in dotCMS - Product Planning
Nov 25, 2024
Unable to reproduce anymore! We can pass for now |
github-project-automation
bot
moved this from Done
to Internal QA
in dotCMS - Product Planning
Dec 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent Issue
#29498
Problem Statement
The job processing loop in JobQueueManagerAPIImpl is failing intermittently with a DotDataException caused by a database connection timeout. This results in an inability to fetch the next job for processing and potentially disrupts job queue management. The error logs indicate the following stack trace:
This problem arose with very little load
Steps to Reproduce
Unfortunately, I do not have a pattern to reproduce this
It started happening on a long-running instance. Like the next day
Acceptance Criteria
We need to revise the Database connection pool configuration (dotCMSPool) and determine if any different configuration can resolve the problem or ensure recovery. Perhaps a dedicated pool or something.
dotCMS Version
main
Proposed Objective
Technical User Experience
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: