Bug 1088120

Summary: Rules Engine can use all available database connections
Product: [Community] Bugzilla Reporter: Simon Green <sgreen>
Component: Internal ToolsAssignee: Simon Green <sgreen>
Status: CLOSED CURRENTRELEASE QA Contact: Simon Green <sgreen>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.4CC: ebaak, jmcdonal, rjoost
Target Milestone: 4.4   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.4.4019 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-07 00:58:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1017534    

Description Simon Green 2014-04-16 05:19:03 UTC 
Description of problem:
When processing many rules, it is possible that the number of available MySQL connections is exhausted.

Version-Release number of selected component (if applicable):
4.4.2018-2

How reproducible:
always

Steps to Reproduce:
1. Add many hundreds of bugs to the Rule Engine


Actual results:
E-mails get sent about "Error: Too many connections", and the web site becomes available. This fixes itself after the script terminates (since DBI cleanup removes those connections when the script exits)


Expected results:
No errors.

Additional info:
Obviously my understanding of how the Job Queue handles database connections is incorrect. I'll look at the mail queue and BMO's generate mail to see how it should be done :)
Comment 2 Simon Green 2014-05-07 00:58:00 UTC 
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

  -- simon