-
Bug
-
Resolution: Fixed
-
P3
-
7u40
-
b53
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8026096 | 8 | Markus Grönlund | P3 | Resolved | Fixed | b111 |
JDK-8020887 | 7u60 | Markus Grönlund | P3 | Resolved | Fixed | b01 |
JDK-8021038 | 7u45 | Markus Grönlund | P3 | Closed | Fixed | b04 |
JDK-8020610 | 7u40 | Markus Grönlund | P3 | Closed | Fixed | b34 |
JDK-8025616 | hs25 | Markus Grönlund | P3 | Resolved | Fixed | b53 |
When I do recordings on GlassFish, I never get any CPU-load-events, even though they are turned on. See the attached recording.
All other events seems to work fine. This is bad since CPU-load-information (one dial and one graph) are on the first page when opening a recording in Mission Control.
All other events seems to work fine. This is bad since CPU-load-information (one dial and one graph) are on the first page when opening a recording in Mission Control.
- backported by
-
JDK-8020887 No CPULoad-events when recording a GlassFish instance
- Resolved
-
JDK-8025616 No CPULoad-events when recording a GlassFish instance
- Resolved
-
JDK-8026096 No CPULoad-events when recording a GlassFish instance
- Resolved
-
JDK-8020610 No CPULoad-events when recording a GlassFish instance
- Closed
-
JDK-8021038 No CPULoad-events when recording a GlassFish instance
- Closed
- relates to
-
JDK-8056049 getProcessCpuLoad() stops working in one process when a different process exits
- Closed
(1 relates to)