[midPoint] handling resource communication errors

[Brad Firestone]

Just adding to the discussion.  I have midPoint 3.9 installed as a 
standalone installation (not Docker) in a VMware installation, and have 
this same problem with one openLDAP server.  It will randomly go into a 
disconnected state.  As soon as I "Test connection" everything is fine.  
Memory and CPU usage is way below capacity so I don't think it's 
performance related, like the Docker issue.

I'm trying to figure out why it loses the connection, checking firewall 
and other network issues.  But it would also be good if I could "Test 
connection" every night to make sure it's working.  I don't know if 
there's some sort of command or URL call that I could schedule to happen 
automatically.

If anyone has any ideas about the automation, or even better, why the 
resource becomes unavailable, that would be great.
Thanks!
Brad


Gómez Martínez, Elsa wrote on 11/7/19 3:36 AM:
>
> Hi!
>
> If I have understood your issue, I have got the same error when using 
> midPoint on Docker, it was very slow and I received a connection timeout.
>
> I solved it by increasing the capacity of Dockers.
>
> I hope it helps.
>
> Elsa
>
> *De:*midPoint <midpoint-bounces at lists.evolveum.com> *En nombre de 
> *Minarciny, Jan
> *Enviado el:* miércoles, 6 de noviembre de 2019 12:34
> *Para:* midpoint at lists.evolveum.com
> *Asunto:* [midPoint] handling resource communication errors
>
> Hi all,
>
> is there any config/automatic way of a situation when a resource gets 
> unavailable (due let's say communication error or connector error) and 
> later gets available again? Because right now it's stuck in "Resource 
> is down" until I manually hit "Test connection" button and all the 
> requests are taking really *longer* time to process (handled error 
> situation).
>
> Thank you for your help,
>
> Johny
>
>
> ------------------------------------------------------------------------
>
> Este correo electrónico y, en su caso, cualquier fichero anexo al 
> mismo, contiene información de carácter confidencial exclusivamente 
> dirigida a su destinatario o destinatarios. Si no es vd. el 
> destinatario indicado, queda notificado que la lectura, utilización, 
> divulgación y/o copia sin autorización está prohibida en virtud de la 
> legislación vigente. En el caso de haber recibido este correo 
> electrónico por error, se ruega notificar inmediatamente esta 
> circunstancia mediante reenvío a la dirección electrónica del remitente.
> Evite imprimir este mensaje si no es estrictamente necesario.
>
> This email and any file attached to it (when applicable) contain(s) 
> confidential information that is exclusively addressed to its 
> recipient(s). If you are not the indicated recipient, you are informed 
> that reading, using, disseminating and/or copying it without 
> authorisation is forbidden in accordance with the legislation in 
> effect. If you have received this email by mistake, please immediately 
> notify the sender of the situation by resending it to their email address.
> Avoid printing this message if it is not absolutely necessary.
>
>
> _______________________________________________
> 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/20191107/0501239a/attachment.htm>