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?
Any mon_config_service probe version
Corrupted mon_config_service instance