Bug 1134437 - Rarely platform process service CPU Percentage metric returns values that are inconsistent with actual CPU load measurements
Summary: Rarely platform process service CPU Percentage metric returns values that are...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Monitoring -- Other
Version: JON 3.2.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: JON 4.0.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-27 13:53 UTC by Jeeva Kandasamy
Modified: 2019-06-24 14:53 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-24 14:53:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
CPU-percentage greater than 200% with two cpu (167.20 KB, application/octet-stream)
2014-08-27 13:53 UTC, Jeeva Kandasamy
no flags Details

Description Jeeva Kandasamy 2014-08-27 13:53:47 UTC
Created attachment 931489 [details]
CPU-percentage greater than 200% with two cpu

on verifying the bug https://bugzilla.redhat.com/show_bug.cgi?id=1091134 found this issue.

CPU-percentage greater than 200% with two cpu

I imported a java process, on the first check it took usage as 206.5%, where I have only two CPUs. Hence I'm reopening this issue.

Steps I followed,
1. Imported a process resource which is down
2. After successful import started the process(java) up and running.
3. very first value of the cpu usage shows as 206.5%, where I had only 2 CPUs
4. I was kept run for an hour,I see problem with only very first value.
5. I restarted the java process service, again I can see the wrong value(570.2%) for the very first value of the CPU usage after restart.

Version: 
JBoss Operations Network
Version : 3.2.0.GA Update 03
Build Number : bca1bc8:e19c43d
GWT Version : 2.5.0
SmartGWT Version : 3.0p


Screen shot is attached.

Comment 2 Filip Brychta 2019-06-24 14:53:58 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.


Note You need to log in before you can comment on or make changes to this bug.