Primary Hub hub.exe memory leak on 20.1

book

Article ID: 197824

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

Since 8/12, the HUB.EXE on our primary hub has started using more and more memory.  Monday night it was consuming 18 GB of ram.  I restarted the server and the memory usage has been steadily growing and is back up to 10 GB.  Prior to 8/12 hub.exe didn't use even 1 gb. 

Cause

Aug 20 13:19:06:466 [9480] 0 hub: (nim_ldap_query) ldap_search_ext_s(base:=OU=Enterprise Command Center,OU=Groups,OU=SA Support,DC=corpint,DC=net scope:=LDAP_SCOPE_SUBTREE filter:= attrs:=userPrincipalName, memberOf, name
Aug 20 13:19:06:466 [9480] 0 hub: (nim_ldap_query) ldap_search_ext_s(base:=OU=Enterprise Command Center,OU=Groups,OU=SA Support,DC=corpint,DC=net, filter:=): Filter Error
Aug 20 13:19:06:466 [9480] 0 hub: access [LDAP] - user_list_groups: ldap_search_ext_s: 'Filter Error' (87)
Aug 20 13:19:06:466 [9480] 0 hub: do_ldap_query [LDAP] - query failed: ldap_search_ext_s: 'Filter Error' (87)
Aug 20 13:19:06:466 [9480] 3 hub: nimSession:000000BA2F5632A0:3892:10.240.13.21/50722:10.240.13.21/50722 - needs cross-thread locking
Aug 20 13:19:06:466 [9480] 3 hub: do_ldap_query [LDAP] finished, time used: 18
Aug 20 13:19:06:468 [3248] 3 hub: nimSession:000000BAA97C8690:3148:10.240.13.21/50729:10.240.13.21/50729 - needs cross-thread locking

 

Filter error 87 is an ldap response error and not a UIM error. 

Environment

Release : 20.1

Component : UIM - HUB

Resolution

Change the ldap search string in the hub probe on the primary uim, save, then change it back.