Reaper counted X sessions but global count is Y sessions

Document ID : KB000094073
Last Modified Date : 02/05/2018
Show Technical Document Details
Issue:

In some ITCM logs following ERROR or WARNING messages like below could be seen :
 
WARNING| ReaperThread : Reaper counted 0 sessions but global count is 1 sessions

or
ERROR  | ReaperThread : Reaper counted 2 sessions but global count is 19 sessions


 
Resolution:

These Warning or Error messages could be ignored. They indicate that some SM (Session Manager) sessions have been opened but never closed.


Example :
 
ERROR  | ReaperThread : Reaper counted 2 sessions but global count is 19 sessions

This line means that there are 2 actives sessions but there are 19 opened sessions. So it means that 17 sessions are not active and not closed.
This problem could occur if there are some network communication problems with a remote computer.


The limit is 7000 opened sessions. If global count is lower than 7000, there is no consequence.
But if global count reaches 7000 sessions, no new session could be opened and network communication is no more possible.

The solution is to restart the plugin.



Example :

If in TRC_AMRSS_0.log, a lot of lines like this one appear :

RSS       |CFSMCAPI        |CFSMCAPI            |000000|ERROR  | ReaperThread : Reaper counted 15 sessions but global count is 7001 sessions


Plugin AMRSS could not accept incoming connections coming form ITCM AM Agent. And AM Inventory could not be done.
amrss plugin must be restarted :
 
caf stop amrss
caf start amrss