Closed sivachandran closed 3 weeks ago
Hello @sivachandran , thanks for your report.
The recording is not really corrupted - it is a valid JFR file, according to all available information about the JFR format. Unfortunately, the jfr
tool is rather picky - when you use eg. JMC to open the recording it will work just fine.
We will look into how to make the jfr
tool happy as well, but it is not the top priority.
I'm able to parse the JFR with another tool.
Thanks for the information.
Hi,
I'm using dd-trace-java outside DataDog eco-system.
I'm profiling(using
dd-java-agent-1.39.0.jar
) a simple Java application(serves pages usingcom.sun.net.httpserver.HttpHandler
) on OpenJDK 21. The generated profile(main.jfr
) seems to be corrupted or malformed. I tried viewing the JFR withjfr
command-line and it is returning the following errorbut the same application profiled on OpenJDK 17 produces valid JFR.
jfr
command-line is able to open and process the JFRAttached the JFR for your reference jfr-profile-openjdk-21.jfr.gz
I also tried profiling on Azul Zulu OpenJDK. The profiles generated from Azul Zulu OpenJDK 17 and 18 both failed with
jfr
command-line with the same error.