You may observe high memory utilization on vIDM nodes, where the Horizon service consumes excessive memory (around 7.5 GB or more).
VMware Identity Manager (vIDM) 3.3.7
horizon.log.Example log entries:
YYYY-mm-dd T23:58:45,147 WARN (sync-scheduling-thread-1) [;;;] com.vmware.vidm.audit.context.AuditContext - POSSIBLE MEMORY LEAK !!! - AuditContext has not been cleared for PT1####9M0.342S (Enable trace to investigate) - AuditContext[id=f2##3f9-5fd8######9193c##9] timestamp=13###805, userId=null, userName=null, userUUID=null, userDomain=null, usersOrganizationId=null, tenantId=null, isActorOperator=false, clientId=null, deviceId=null, userId=null, workspaceId=null, sourceIp=null, userExternalId=null, deviceType=null]
YYYY-mm-dd T23:58:45,149 WARN (sync-scheduling-thread-1) [;;;] com.vmware.vidm.audit.context.AuditContext - POSSIBLE MEMORY LEAK !!! - AuditContext has not been cleared for PT13#####59M0.344S (Enable trace to investigate) - AuditContext[id=f2##a3f3######e-107f91##3d9] timestamp=17581#####4805, userId=null, userName=null, userUUID=null, userDomain=null, usersOrganizationId=null, tenantId=null, isActorOperator=false, clientId=null, deviceId=null, userId=null, workspaceId=null, sourceIp=null, userExternalId=null, deviceType=null]
YYYY-mm-dd T23:59:19,991 INFO (tomcat-http--27) [MN#####T0DS1;-;1xxxx.7;] com.vmware.horizon.components.oauth2.provider.xxxerviceImpl - Comparing OAxxient Row Id2301and Request Client Row Id23
Workaround:
Restart the horizon-services on all the 3 nodes or just the affected nodes.
Broadcom Product Engineering is aware of this behavior and is working on a permanent fix in a future release.