|
Type:
|
Bug
|
|
Priority:
|
Low
|
|
Severity:
|
Trivial
|
|
Status:
|
Closed
|
|
Resolution:
|
Complete
|
|
Resources:
|
Bob Denny
|
|
Reported By:
|
Bob Denny
|
|
Component:
|
Dispatch Scheduler Engine
|
|
Versions Affected:
|
3.7
|
|
Start Date:
|
11/12/2014
|
| Created: |
11/12/2014 9:45:38 AM |
| Revised: |
11/12/2014 10:51:59 AM
|
| Closed: |
11/12/2014 10:51:59 AM |
| Resolved: |
11/12/2014 10:51:55 AM |
|
See this Comm Center thread from Paul Gardner. The dispatcher magically starts after restarting the scheduler (from an "operator intervention" failure). This is due to ACP's Util.Scheduler.DispatcherEnabled variable being True from the last Scheduler run. When starting Scheduler, and when attaching ACP, force this variable to False right then and there.
|
|
|
|
|
|
|
|
|
|
|
|
Are you sure that you want to reset the votes?
