Hi all,

we are running Sentinel 7.3.0.1 and we are getting several of these
messages in server0.0.log almost every 2 minutes:

Code:
--------------------
Tue Dec 15 14:12:03 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor is unable to keep up with status update messages.
--------------------


Sometimes there are few of these messages:

Code:
--------------------
Tue Dec 15 11:12:03 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor executor queue not purged.
--------------------


After turning log level to ALL for CollectionHealthMonitor class the
entire process looks like that:

Code:
--------------------
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor status update: full
Tue Dec 15 15:23:57 CET 2015|FINE|pool-35-thread-1|esecurity.ccs.comp.proxycollector.api.Collection HealthMonitor$UpdateTask.run
Collection Node Health Monitor Task: Update Health Data for multiple nodes is starting.
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor status update: full
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor signalling running task to abort.
Tue Dec 15 15:23:57 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor is unable to keep up with status update messages.
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor status update: full
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor signalling running task to abort.
Tue Dec 15 15:23:57 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor is unable to keep up with status update messages.
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor status update: full
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor signalling running task to abort.
Tue Dec 15 15:23:57 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor is unable to keep up with status update messages.
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor status update: full
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor signalling running task to abort.
Tue Dec 15 15:23:57 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor is unable to keep up with status update messages.
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor status update: full
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor signalling running task to abort.
Tue Dec 15 15:23:57 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor is unable to keep up with status update messages.
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor status update: full
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor signalling running task to abort.
Tue Dec 15 15:23:57 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor is unable to keep up with status update messages.
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor status update: full
Tue Dec 15 15:23:57 CET 2015|FINE|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor signalling running task to abort.
Tue Dec 15 15:23:57 CET 2015|WARNING|Service Manager pool|esecurity.ccs.comp.proxycollector.api.Collect ionHealthMonitor.updateHealth
Collection Node Health Monitor is unable to keep up with status update messages.
Tue Dec 15 15:23:57 CET 2015|FINE|pool-35-thread-1|esecurity.ccs.comp.proxycollector.api.Collection HealthMonitor$UpdateTask.run
Collection Node Health Monitor Task: Update Health Data for multiple nodes completed.
Tue Dec 15 15:23:57 CET 2015|FINE|pool-35-thread-1|esecurity.ccs.comp.proxycollector.api.Collection HealthMonitor$UpdateTask.run
Collection Node Health Monitor Task: Update Health Data for multiple nodes is starting.
Tue Dec 15 15:23:57 CET 2015|FINE|pool-35-thread-1|esecurity.ccs.comp.proxycollector.api.Collection HealthMonitor$UpdateTask.run
Collection Node Health Monitor Task: Update Health Data for multiple nodes completed.
--------------------


The method updateHealth seems to run only in one thread.

We are not able to discover, what is causing these warning mesages, does
anybody know?
Why is the full update called so many times which causes aborting
previous task?
Are these warnings effortless and can be turned off to prevent spamming
of log files?

Thak you for your help.


--
jakubmichl
------------------------------------------------------------------------
jakubmichl's Profile: https://forums.netiq.com/member.php?userid=7919
View this thread: https://forums.netiq.com/showthread.php?t=54931