Is there is a bug in HPC R2 - submitting additional tasks nullifies the job object? RRS feed

  • General discussion

  • I'm doing the following steps:

    1. Creating a job and a single task from it (task A).

    2. Task A creates sub-tasks from within (A1...An) and another task B dependent on them. Then these tasks are submitted (ISchedulerJob.SubmitTasks). ISchedulerJob is retrieved by GetJobList with a filter by name.

    Before calling SubmitTasks, my job object has a valid name and ID. After the call, the name is empty and the ID is -1. This requires me to retrieve the job again, and then I receive it in a proper state.

    I assume this behavior is unplanned.


    Please let me know if I'm mistaken.


    Best regards,


    Thursday, June 17, 2010 8:34 AM

All replies

  • Hi Alex,

    Thank you for reporting this issue. It has been reproduced and added to our bug tracking system.

    As a temporary workaround I can suggest calling Refresh() method on the job object just after SubmitTasks() call. Will this work for you?

    Thank you,

    Friday, June 18, 2010 2:46 PM
  • This issue will be fixed in RC.


    Tuesday, June 22, 2010 3:40 AM