Reporter server consumes high CPU without any operations

Document ID : KB000087070
Last Modified Date : 14/04/2018
Show Technical Document Details
Affects Release version(s): 3

Error Message :
There is no error message.

Patch level detected:Reporter 3.0.9
High CPU consumption appears on the Reporter server for brutally dropped connections from UVC or Reporter CLI because of an infinite loop in the communication layer.

The CPU consumption remains high without any Reporter operations.
For example, the unicheckrep command shows that there is no Reporter operations but the top command shows the Reporter process is consuming about 101% of the CPU.

# ./unicheckrep
REPNODE=support2 value taken from configuration file server.conf.
Reporter Server name = support2
Reporter Server PID = 6105
noOfPurgesInExec = 0
noOfPurgesInWait = 0
noOfExtractionsInExec = 0
noOfExtractionsInWait = 0
noOfReportsGenerateInExec = 0
noOfReportsGenerateInWait = 0
memUsage = 258.8777
memFree = 651.3723

Result of the top command:
# top -b -n 2 |grep 6105
6105 root 20 0 1763m 756m 4720 S 101.5 19.2 19076:18 java

On Windows, the same anomaly can be observed from the Windows Task Manager.
OS: All
OS Version: ALL OS
Cause type:
Root Cause: This is a bug affecting Reporter 3 versions
Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Reporter 3.0.10 - Available
Additional Information:
Workaround :
Restart Reporter Server