[SCHEDULER-1313]  Failure to initialize sequencer results in zombie Scheduler
Type Bug
Priority Low
Severity Trivial
Component Dispatch Scheduler Engine
Fixed In Version [8.0] 8.0
Versions Affected [3.7] 3.7
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 3/11/2015

Description 
I found this while testing the version locking with a mismatch. If ACPSequencer.Attach() fails and throws, a chain of events results in the Engine.Status = Dead, and in the MainForm loading this results in an infinite loop waiting for the engine to initialize.

Comments
3/11/2015 7:14:37 PM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

  Repository
  svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 

 

  SVN Revision
  554
 

 

  Affected files
  /trunk/Help/RelNotes.htm (Modified)
/trunk/Scheduler/ACPSequencer.cs (Modified)
/trunk/Scheduler/MainForm.cs (Modified)

 

 

  Check-in comment
  For ACP 8.0, prevent engine attach problems from resulting in zombie Scheduler.exe. Pop up a message box if there is a version mismatch between Scheduler and ACP.
GEM:1313