Bug 1250305 - Ensure the job queue catches any errors and logs them properly
Summary: Ensure the job queue catches any errors and logs them properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 4.4
Assignee: Jeff Fearn 🐞
QA Contact: Rony Gong 🔥
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-05 05:25 UTC by Jeff Fearn 🐞
Modified: 2018-12-09 06:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-20 23:28:41 UTC
Embargoed:

Attachments (Terms of Use)

Description Jeff Fearn 🐞 2015-08-05 05:25:06 UTC 
Description of problem:
Currently the job queue can terminate and not log an event for why or when it terminated. Need to be able to guarantee an event is logged whenever the job runner terminates.
Comment 1 Jeff Fearn 🐞 2015-08-17 05:56:13 UTC 
Couple of ways to test this.

1: run a stress test, it's bound to cause serialization errors which should go in to the BZ log, not in to the error log.

2: add some jobs to the job queue with he queue disabled, then edit the db to set ts_job.run_after to empty string or a negative number or something weird, this might trigger an error that again should go in the standard log.
Comment 2 Rony Gong 🔥 2015-08-17 08:19:59 UTC 
Tested on 
QA environment(bzperfweb01.app.qa) with version(4.4.9039-1, DB: psql )
Result: Pass
Comment 3 Matt Tyson 🤬 2015-09-20 23:28:41 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.
Note You need to log in before you can comment on or make changes to this bug.