Thanks Anjana.

Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

On Thu, Nov 27, 2014 at 2:38 PM, Anjana Fernando <anj...@wso2.com> wrote:

> Hi Ishara,
>
> These are rough mappings to the Quartz properties that they have, only
> FINISHED here is COMPLETED of them. There are some descriptions of those
> here [1]. Basically a summary would be:-
>
> * NORMAL: The task is scheduled to run, but an actual execution of the
> task is not happening at the moment, for example, if its to run in 1 minute
> intervals, and if it executed lastly at 0 seconds, which took 3 seconds to
> execute, from 4 - 59 seconds, it will be in NORMAL state.
> * PAUSED: The task is paused, executions will not happen
> * FINISHED: The task executions are finished, for example, if a limit on a
> execution count is given, if will finish eventually
> * NONE: There is no such task scheduled
> * BLOCKED: An execution of a scheduled task is happening now, this happens
> in times like, 0 - 2 seconds in my earlier example, and again starting at
> 60 seconds
> * UNKNOWN: Some unexpected error/state, which normally shouldn't occur
>
> [1] http://www.docjar.com/docs/api/org/quartz/Trigger.html
>
> Cheers,
> Anjana.
>
> On Thu, Nov 27, 2014 at 2:09 PM, Ishara Cooray <isha...@wso2.com> wrote:
>
>> Hi Anjana,
>>
>> NORMAL, PAUSED, ERROR, FINISHED, NONE, BLOCKED, UNKNOWN are the task
>> states that a particular task can have.
>> Could you please clarify in which scenarios a task can go into these
>> states?
>>
>> Also how can we identify a particular task is not scheduled properly?
>>
>>
>> Thanks & Regards,
>>
>> Ishara Cooray
>> Senior Software Engineer
>> Mobile : +9477 262 9512
>> WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to