P4
JFR already supports (JDK) events for class loading occurences, but these events do not include metadata such as the identity of the .class file from
which they are loaded nor the module (if any) that they are contained within.
audit tools such as the Java Mgmt Service which capture a broad variety of
such metadata for subsequent auditing and analysis would benefit from the
addition of class loading metadata such as the .class file origin and the enclosing module name
which they are loaded nor the module (if any) that they are contained within.
audit tools such as the Java Mgmt Service which capture a broad variety of
such metadata for subsequent auditing and analysis would benefit from the
addition of class loading metadata such as the .class file origin and the enclosing module name
- causes
-
JDK-8373122 JFR build failure with CDS disabled due to -Werror=unused-function after JDK-8365400
-
- Open
-
-
-
- Resolved
-
- relates to
-
JDK-8373028 Resolve inconsistency in class loading source paths between normal and AOT class loading
-
- Open
-
- links to
-
Commit(master)
openjdk/jdk/e93b10d0
-
Review(master)
openjdk/jdk/28505