My Oracle Support Banner

How to detect and fix healthcheck restarts caused by high memory/CPU usage in Oracle Communications Session Monitor / Palladion 3.x ? (Doc ID 1915553.1)

Last updated on MARCH 18, 2022

Applies to:

Oracle Communications Session Monitor - Version 3.3.90 to 3.3.90 [Release 3.0]
Oracle Communications Session Monitor - Version 3.3.x to 3.3.x [Release 3.0]
Information in this document applies to any platform.


Drops in graphs or service/traffic interruption. Especially if occurring on a probe or ME+probe, temporary packet loss (due to the sniffing services getting restarted).

Here is an example for a very obvious drop in the Active calls graph:


This issue usually starts to appear because the system is using more memory or CPU than the current configured thresholds - for example after adding new devices, users, concurrent calls etc. Also, even after you fix it by using the solution below, it might reappear after a while so you might need to apply the solution again.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Graph drops once a week
 Understanding the healthcheck service
 Detecting restarts caused by the healthcheck limits
 Memory Limit 1 - "service_high_mem"
 Memory Limit 2 - "service_very_high_mem"
 CPU limit - "service_cputime"
 Adjusting the limits
 Version <
 Version >=

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.