-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 17, 19
-
Component/s: hotspot
-
b23
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8328672 | 17.0.12-oracle | Joe Cherian | P3 | Resolved | Fixed | b01 |
| JDK-8328159 | 17.0.12 | Jaroslav Bachorík | P3 | Resolved | Fixed | b01 |
The timestamp for the jdk.ActiveSetting event is cached so it always the same during the lifetime of the JVM. This also leads to the event getting a duration, i.e 0.190 ms, instead 0 s.
The event is also emitted twice when a new recording is started.
This bug fix should be considered for a backport. It was introduced in JDK 14 with Event Streaming.
The event is also emitted twice when a new recording is started.
This bug fix should be considered for a backport. It was introduced in JDK 14 with Event Streaming.
- backported by
-
JDK-8328159 JFR: Active Setting event emitted incorrectly
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8286688 JFR: Active Setting events should have the same timestamp
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/4b9ab0dd
-
Commit
openjdk/jdk/24cab0af
-
Review
openjdk/jdk17u-dev/2210
-
Review
openjdk/jdk/8709
(2 links to)