[midPoint] Persistent Tasks
Pavol Mederly
mederly at evolveum.com
Mon Dec 14 09:55:01 CET 2015
Hello Samu,
a task should go into a "suspended" state only if the problem that
occurred is believed to be a persistent one. Transient problems like "AD
down" should not result in the task being suspended - i.e. the
synchronization task should report an error, but it should continue trying.
There might be a bug in midPoint that incorrectly treats such an error.
Or, maybe, the connector reports the problem in a wrong way. (This
midPoint-connector-resource interplay is sometimes quite tricky.)
Would you please share your log file for us to diagnose the problem further?
Best regards,
Pavol
On 14. 12. 2015 9:32, Samu Viitanen wrote:
> Hello,
>
> I came across an issue where I would like a synchronization task to be
> "persistent" meaning it would attempt to resume the task every once in
> awhile in case it was suspended. I do not want to use the
> administration interface to restart suspended tasks. I understand that
> it might be stupid to keep resuming a broken task, but if an AD is
> down for example, the task would never resume even if it came back up?
> Is this possible currently in midPoint?
>
> BR.
>
> Samu Viitanen
>
>
> _______________________________________________
> 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/20151214/1bf0c557/attachment.htm>
More information about the midPoint
mailing list