[midPoint] Persistent Tasks
Samu Viitanen
zamppa90 at hotmail.com
Mon Dec 14 14:13:22 CET 2015
After more thorough investigation I noticed that the Task is executing correctly. The task is suspended only in situations like: shutting down the Connector Server machine or a similar persistent situation. If the connector server service running on the machine is shut down, an error message is shown and the task indicates a red circle with a dash in it, but it is still running as Pavol explained. When the service is brought back up, the synchronization continues normally. I have not tested what would happen if the AD machine was shut down, but the AD machine shutting down would be a catastrophe anyways.
I did not file a bug, I will keep monitoring the situation to see if there really is a bug.
To: midpoint at lists.evolveum.com
From: mederly at evolveum.com
Date: Mon, 14 Dec 2015 10:26:13 +0100
Subject: Re: [midPoint] Persistent Tasks
Samu,
this is a clear bug. It shouldn't show "Suspended" in this
situation. Please, could you log it into jira? (with "how to
replicate" indiciation?)
Thank you
PAvol
Hello Pavol,
Thank you for your quick response. Now that I investigated my
logs a bit more, I noticed that the sync task is indeed still
trying to connect to the AD, it just shows "Suspended" in the
administration interface. I think I can continue with my
implementation. Thank you for clarifying this for me.
Maybe the UI should show something else than "Suspended" when a
transient problem happens.
BR,
Samu
To: midpoint at lists.evolveum.com
From: mederly at evolveum.com
Date: Mon, 14 Dec 2015 09:55:01 +0100
Subject: Re: [midPoint] Persistent Tasks
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
_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint
_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint
_______________________________________________
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/43a17a0a/attachment.htm>
More information about the midPoint
mailing list