mon_config_service probe is spawning multiple process instances and consumes system memory usage

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We noticed that the mon_config_service probe spawns multiple process instances and consumes system memory usage.

In some cases, the mon_config_service.log logsize setting is not honored and the mon_config_service probe generates a mcs_fatal.log file located in the X:\Nimsoft\probes\service\mon_config_service folder with the entry below:

java.lang.OutOfMemoryError: unable to create new native thread

How can we resolve this?

Environment

Any mon_config_service probe version

Cause

Corrupted mon_config_service instance

Resolution

1. Ensure that the Nimsoft root directory and all sub-directories are EXCLUDED from being scanned by Antivirus scanning. See Antivirus scanning of UIM components knowledge article for additional information.

2. Deactivate and delete the mon_config_service probe 

3. Kill any existing mon_config_service processes and delete/rename the probes/service/mon_config_service folder

4. Stop the Nimsoft Robot Watcher service and wait for 5 mins 

5. Start the Nimsoft Robot Watcher service and deploy the mon_config_service