[midPoint] rescheduling server task after error

[Pavol Mederly]

Hello Oskar,

the problem is that the task goes to suspended state, right?

Looking at JobExecutor:486, this behavior is currently hardcoded. It is 
not a big deal to introduce appropriate configuration parameter, but it 
would require some design thinking.

Pavol Mederly
Software developer
evolveum.com

On 06.09.2017 11:08, Oskar Butovič - AMI Praha a.s. wrote:
> Hello everybody!
>
> We have certain server tasks, for example, reconcilliation of GA 
> groups, which sometimes fails but next run is usually ok because all 
> data inconsistencies got fixed by the previously failed task execution.
>
> We would like to run again those tasks even though they have (fatally) 
> failed before. I was unable to find the correct scheduling 
> configuration to enforce this behavior. Is it configured only by 
> Misfire action and Thread stop action or are there any other hidden 
> configuration parameters? What should be correct configuration to 
> execute a failed task on next scheduled interval or right after fail?
>
> Best Regards
> Oskar Butovič
> -- 
>
> Oskar Butovič
> solution architect
>
> gsm: [+420] 774 480 101
> e-mail: oskar.butovic at ami.cz <mailto:oskar.butovic at ami.cz>
>
> 			
>
> AMI Praha a.s.
> Pláničkova 11
> 162 00 Praha 6
> tel.: [+420] 274 783 239
> web: www.ami.cz <http://www.ami.cz/>
>
> 			
>
> AMI Praha a.s.
>
>
> AMI Praha a.s. 
> <http://www.ami.cz/reseni-a-sluzby/bezpecnost-dat/identity-management>
>
> Textem tohoto e-mailu podepisující neslibuje uzavřít ani neuzavírá za 
> společnost AMI Praha a.s.
> jakoukoliv smlouvu. Každá smlouva, pokud bude uzavřena, musí mít 
> výhradně písemnou formu.
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170906/6ee1b7c4/attachment.htm>