[OPENIDM-1664] Memory usage of AD connector continue to increase. Created: 12/Mar/14 Updated: 19/Oct/16 Resolved: 18/Oct/16
|Component/s:||Plugin - AD account change handler|
|Affects Version/s:||OpenIDM 2.1.0|
|Fix Version/s:||OpenIDM 5.0.0|
|Reporter:||Toru Tanaka [X] (Inactive)||Assignee:||Chris Drake|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
environment :OpenIDM #1 (single server)
This problem is reported by OGIS-RI.
As AD connector contiune to run,
Attachment is screenshot while "ConnectorServer.exe" private working set is increasing.
|Comment by Toru Tanaka [X] (Inactive) [ 20/Mar/14 ]|
This file is svn diff that OGIS-RI made for this problem.
|Comment by Toru Tanaka [X] (Inactive) [ 13/Jul/15 ]|
Same problem happen in OpenIDM 3.2 Snapshot.
|Comment by Gael Allioux [ 28/Jul/15 ]|
The problem you are referring to is not related to OpenIDM version but to Active Directory .Net connector.
I have worked on that memory leak problem a while ago and found out that it was actually coming from the underlying COM objects components (ADSI in particular) and not
The usage of System.GC.Collect() is usually not recommended...
|Comment by Mike Jang [X] (Inactive) [ 30/Dec/15 ]|
should this be listed as an OpenICF issue for those release notes?
|Comment by Chris Drake [ 18/Oct/16 ]|
Closing this issue as the AD Connector is deprecated and this issue will not be intvestigated further. The recommendation is to use the LDAP Connector or PowerShell Connector to connect to AD going forward.