#1509 closed enhancement (fixed)
Job queue order after restarting a job
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | major | Milestone: | BASE 2.16 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
The job queue is ordering jobs based on their creation date+time. This leads to a shortcut for some jobs to get first in the queue after a restart. A job may be restarted for example after a failure or after a dry-run. Since the creation date can't be modified I think we should add a new column (scheduled date) that is used for the queue order and that is updated to the current time after a restart.
A particular loophole was introduced by #1503. Consider a job queue that allows only one executing job at a time and a malicious plug-in that always respond with setContinue(). This will cause the same job to be added first in the queue, blocking all other jobs from ever being executed.
Change History (5)
comment:1 by , 14 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 14 years ago
comment:3 by , 14 years ago
comment:4 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:5 by , 14 years ago
(In [5414]) References #1509: Job queue order after restarting a job
Fixes a potential NullPointerException. 16 test programs failed since they don't use the signaling system.
(In [5406]) References #1509: Job queue order after restarting a job
Added a 'scheduled' property to jobs that is used to order the job queue.