[OPENIDM-1664] Memory usage of AD connector continue to increase. Created: 12/Mar/14  Updated: 19/Oct/16  Resolved: 18/Oct/16

Status: Closed
Project: OpenIDM
Component/s: Plugin - AD account change handler
Affects Version/s: OpenIDM 2.1.0
Fix Version/s: OpenIDM 5.0.0

Type: Bug Priority: Major
Reporter: Toru Tanaka [X] (Inactive) Assignee: Chris Drake
Resolution: Expired Votes: 0
Labels: OpenIDM, release-notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

environment :OpenIDM #1 (single server)
version :2.1.0 (source build)
OS(AD) :Windows Server 2008R2 (AD connector run on this server.)
Other :.NETframework 4.0

Attachments: Text File ActiveDirectoryConnector.cs.patch     PNG File screenshot.4.png    


This problem is reported by OGIS-RI.

As AD connector contiune to run,
memory usage countinue to incrase on Windows Sever that AD connector run.
As far as we confirm OS function did not relaease the memory.
*Surely, this problem is also related to .NETworkframework.

to do provisioning(including update) or reconciliation over again and again.

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.
It is possible to fix same modification of OpenIDM 2.1.

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 .Net "virtual machine" (memory usage was stable with time)

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.

Generated at Fri Sep 25 21:52:44 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.