[midPoint] AD LDAP resource memory usage

[Radovan Semancik]

Hi,

The root problem is, that "generationConstraints" is a midPoint concept. 
ConnId framework does not know about it. Therefore the connector has to 
download a complete LDAP schema. What makes it even worse is that the 
ConnId framework does not have any proper mechanism to share data 
between connector instances. Therefore each connector instance has to 
keep the schema separately. This may be also combined in changes in 
Apache Directory API that might also increase the memory consumption for 
the schema. Systematic solution to this problem will need changes to 
ConnId framework.

However, in your case the XML should not have 100MB. Maybe this is just 
a "fallout" of a bug related to generationConstraints. That bug should 
be fixed now. Please try to delete the <schema> part of the resource and 
keep just the generationConstraints. The schema should be re-generated 
and it should be considerable smaller.

See also: https://jira.evolveum.com/browse/MID-5284

-- 
Radovan Semancik
Software Architect
evolveum.com



On 5/29/19 9:25 AM, Davy Priem wrote:
> Hi,
>
> Suddenly I’m having issues with an AD LDAP resource consuming lots of memory which makes midpoint very slow. When I download the resource, the XML is 100MB in size. I don’t know why the schema suddenly became so big. I’ve cheched the resource and the generationConstraints  as mentioned bellow, is still there. Anyone having the same issue? I’ve tested with latest support-3.9 (standalone on centos 7) in combination with ADLDAP connector 1.6.1, 2.0 and 2.1.
>
> <schema>
>     <generationConstraints>
>          <generateObjectClass>ri:user</generateObjectClass>
>          <generateObjectClass>ri:group</generateObjectClass>
>      </generationConstraints>
> </schema>
>
> Best regards,
> Davy Priem
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint