Print

[jherrerah]

When I schedule a task and the node that runs it has a problem that makes the task can not be terminated except for the time limit is triggered, according to the millisecond that are programmed and can perform some task to correct this problem. When the task is not any node to execute the task remains in a state undertakes no indefinitely. You can capture any exception in this case?

[lolo]

Hello,

I am not sure I understand the problem you are describing, would you mind elaborating?
Here is what I understand, please feel free to correct me when needed:
- you submitted a task, and while this task was running, the ode on which it was running had a problem. Can you tell us what that problem was?
- you are talking about a time limit that was triggered, so I'm assuming you set a task timeout using JPPFTask.setTimeout(...) or something equivalent, is this correct? If yes, I'm also assuming you implemented the onTimeout() method in your task, can you confirm as well?
- the main problem is what happens to a task when it is not executing in a node, and there is no node to execute it? In this case, I would recommend to set a timeout on the job that contains the task, so the job will be cancelled when the timeout expires, and it won't remain indefinitely hanging.

Does this answer your question?

Sincerely,
-Laurent

[jherrerah]

Hello Laurent.

The thrid option is correct. Some task must be run in a especific node. If the node is not up, the task wait until timeout on the job. After reading the chapter "Job start and expiration scheduling" I coded a job that expire after some seconds. Everything works fine.

There is a method like JPPFTask.onTimeout() for jobs like JPPFJob.onTimeout() that implement a error handling rutine? If SLA expiration time end, how I can capture it? Some exception raise or  Return null values? I am using null values verification, is that correct?

thanks for the help