Bug Fix:  When a user removed a task from the XML after Rocoto had already submitted a job for it, Rocoto still tries to track the           job for the undefined task.  The problem was that when the state of the job was updated, Rocoto tried to get information            about the now undefined task associated with the job.  This has been fixed by:
Bug Fix:  When a user removed a task from the XML after Rocoto had already submitted a job for it, Rocoto still tries to track the
          job for the undefined task.  The problem was that when the state of the job was updated, Rocoto tried to get information 
          about the now undefined task associated with the job.  This has been fixed by:

          1) Not attempting to detect hangs for jobs whose task has become undefined
          2) Not attempting to detect expiration for jobs whose task has become undefined
          3) Setting the maxtries for jobs whose task has become undefined to the current try count

          At some point, it may make sense to stop tracking these jobs and simply kill them when it is detected that the task is
          no longer defined.


christopherwharrop/rocoto,christopherwharrop/rocoto