[midPoint] handling resource communication errors

Thu Nov 7 21:45:20 CET 2019

Hello,

I got similaire issue (I'm in Mp 3.7 under docker), I have identifier few case :

  *   Bad connector code : Depand on connector, I get it on custom connector, some action was not correlty handle and down the ressource (in my case, shadow error create ressource down)
  *   Postgre tuning : Since few weeks I have make some tuning in postgre work_mem, max_connection and shared_mem, I really got improvement in midpoint global reaction
  *   Docker / network issue : In case of communication internal (MP in container and Ressource in container under the same swarm cluster) you cas use docker network alias for create direct communication (check docker doc)

Hope that help..

Nota : MP rest API give entrypoint for test resource, that can be a workaroud.

Cordialement,

[https://attachment.outlook.office.net/owa/sylvaire-kevin.tipa@mythalesgroup.io/service.svc/s/GetFileAttachment?id=AAMkAGY1ZjY5NWRmLTQ0ZDgtNGNjMy05NzNkLWJmMDRiMWE1MzRlZABGAAAAAABh4WdBWT4xR7DMeIEaHdTyBwAoAS%2FqG5cHS6e%2BmMV1HZP5AAAAAAEJAAAoAS%2FqG5cHS6e%2BmMV1HZP5AAA6Qq2YAAABEgAQABu5cy33gBtFlMD7DO8YR0A%3D&X-OWA-CANARY=ChiPfpk72ke8XYNev7RaMjBqkl3Gx9UY9Eb1nD0ESaO9Vu49v6lQFICf4be4xrzkFIas0KMHQr8.&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IjA2MDBGOUY2NzQ2MjA3MzdFNzM0MDRFMjg3QzQ1QTgxOENCN0NFQjgiLCJ4NXQiOiJCZ0Q1OW5SaUJ6Zm5OQVRpaDhSYWdZeTN6cmciLCJ0eXAiOiJKV1QifQ.eyJ2ZXIiOiJFeGNoYW5nZS5DYWxsYmFjay5WMSIsImFwcGN0eHNlbmRlciI6Ik93YURvd25sb2FkQGNkOTQzYmVhLTZjYmQtNGI1Mi05ZWVkLTY1MDE1MjYwMzBlYSIsImFwcGN0eCI6IntcIm1zZXhjaHByb3RcIjpcIm93YVwiLFwicHJpbWFyeXNpZFwiOlwiUy0xLTUtMjEtMTg2Mjg2NDE5LTE3ODA1Mzc0ODItMzc3MTQ0MjUwMy0xNzA1MDkzXCIsXCJwdWlkXCI6XCIxMTUzODM2Mjk2ODEyMDA2MTcyXCIsXCJvaWRcIjpcImUwNDllZjY1LTA3OTctNGFlNC04YTlkLTI4ZDg4NTU5ZDAzMVwiLFwic2NvcGVcIjpcIk93YURvd25sb2FkXCJ9IiwibmJmIjoxNTI3ODYwODc3LCJleHAiOjE1Mjc4NjE0NzcsImlzcyI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMEBjZDk0M2JlYS02Y2JkLTRiNTItOWVlZC02NTAxNTI2MDMwZWEiLCJhdWQiOiIwMDAwMDAwMi0wMDAwLTBmZjEtY2UwMC0wMDAwMDAwMDAwMDAvYXR0YWNobWVudC5vdXRsb29rLm9mZmljZS5uZXRAY2Q5NDNiZWEtNmNiZC00YjUyLTllZWQtNjUwMTUyNjAzMGVhIn0.nd8YaoCszRU3J-pTpf2fo2Sjs4X8EeyDVIGRODX-WaLwtbDHAXqMEVMw2_wldyedQ07nJYXTXI7yJ8JwPB09H30wKs9ytHcuchZNPhJZWc6x2ssYRUfiW4dtcuFpSIV16vXS_Lu61-cjbcKGtHNAbGDYFgKiv3vMLzge_N95-xkvLd0GDbPrk743gK0l9TUIjfLTgnrK2uqlSwpVRUeL_dSG-_kKqaMyvJNo0Eh55dKUckmZhws2shczl72V4Ftt-dWzklX6lDGZ6goiYMWb3i0T-_QekdsXRNXlCRO7nIUSlBRndBjtfCMaOE40RBI9lcp9VQKmxWAWQDJpNEUhtQ&owa=outlook.office365.com&isImagePreview=True]

Sylvaire-Kevin TIPA
Thales Services / OIC / DevOps Automatisation Infrastructures
…………………………………………………………………………………………
THALES SERVICES SAS
44 Quai Charles de Gaulle
CS 20100
69463 Lyon Cedex 06
…………………………………………………………………………………………
www.thalesgroup.com<http://www.thalesgroup.com/>

________________________________
De : midPoint <midpoint-bounces at lists.evolveum.com> de la part de Frédéric Lohier <frederic at lohier.org>
Envoyé : jeudi 7 novembre 2019 18:59
À : midPoint General Discussion <midpoint at lists.evolveum.com>
Objet : Re: [midPoint] handling resource communication errors

Hello,

You test your resource using REST API like described here https://wiki.evolveum.com/plugins/servlet/mobile?contentId=13074536#RESTAPI-TestResource(OpenDJ)

-Frederic

On Thu, Nov 7, 2019, 15:26 Brad Firestone <bhotrock at gmail.com<mailto:bhotrock at gmail.com>> wrote:
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><mailto: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<mailto: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<mailto:midPoint at lists.evolveum.com>
http://lists.evolveum.com/mailman/listinfo/midpoint

_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com<mailto:midPoint at lists.evolveum.com>
http://lists.evolveum.com/mailman/listinfo/midpoint

This message contains confidential information and is intended only for the individual(s) addressed in the message. If you are not the named addressee, you should not disseminate, distribute, or copy this e-mail. If you are not the intended recipient, you are notified that disclosing, distributing, or copying this e-mail is strictly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20191107/62821438/attachment.htm>