if (WorkflowExecutor.IsIrrecoverableException(e))
{
throw;
- } //@@undone: for [....]:- we should not be running exception handler, when we are unlocking.
+ } //@@undone: for Microsoft:- we should not be running exception handler, when we are unlocking.
else if (this.WorkflowStatus != WorkflowStatus.Suspended && this.IsInstanceValid)
{
// the persistence attempt threw an exception
}
}
- // shutsdown the schedule instance [....]
+ // shutsdown the schedule instance sync
internal void Unload()
{
WorkflowTrace.Runtime.TraceEvent(TraceEventType.Information, 0, "Workflow Runtime: WorkflowExecutor: Got an unload request for instance {0}", this.InstanceIdString);
#region Terminate
- // terminates the schedule instance [....]
+ // terminates the schedule instance sync
// must be called only from outside the instance... the thread running the instance must
// never call this method... it should call TerminateOnIdle instead.
internal void Terminate(string error)
#region Abort
- // aborts the schedule instance [....]
+ // aborts the schedule instance sync
// must be called only from outside the instance... the thread running the instance must
// never call this method... it should call AbortOnIdle instead.
internal void Abort()
#region Suspend
- // suspends the schedule instance [....]
+ // suspends the schedule instance sync
// must be called only from outside the instance... the thread running the instance must
// never call this method... it should call SuspendOnIdle instead.
internal bool Suspend(string error)
#region Resume
- // resumes the schedule instance [....]
+ // resumes the schedule instance sync
// must be called only from outside the instance... the thread running the instance must
// never call this method... it should call ResumeOnIdle instead.
internal void Resume()
//@@Undone-- bmalhi there is one test in bat
//which fails here. This check is right thing but im
//commenting it out for bat.
- // [....]: this fails because when we load an instance into memory it grabs
+ // Microsoft: this fails because when we load an instance into memory it grabs
// the scheduler lock and starts running. By the time the user Resume request
// gets the scheduler lock the instance is often done (the AbortBat test case scenario)
// Balinder is attempting a fix to separate rehydration from resuming execution.