How to use CrashAnalysis tool to realize jvm hs_err_pid.log File Analysis
This article will explain in detail how to use CrashAnalysis tools to achieve jvm hs_err_pid.log file analysis, the content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.
CrashAnalysis
CrashAnalysis is a diagnostic tool. It is written by a member of an APM project team, which classifies common problems and gives solutions or directions to help us locate problems. Here is the github address of the tool:
Https://github.com/xpbob/CrashAnalysis
Using tutorials
CrashAnalysis is very simple and user-friendly to use. Enter log as a parameter into java-jar CrashAnalysis-1.0-SNAPSHOT.jar ${hs_err_pid.log} by executing the jar command
Java-jar CrashAnalysis-1.0-SNAPSHOT.jar ${hs_err_pid.log}
The CrashAnalysis-1.0-SNAPSHOT.jar file is packaged in the above warehouse and can be downloaded and used directly. It is much easier to use than to read the hs_err_pid.log file.
By default, it is compiled with jdk 1.8. if your jdk version is too low, it is recommended that you download the code and compile the jar file yourself.
Diagnostic effect
After executing the above command, there will be a tab page of diagnostic information, which will tell us the results of the analysis. For example, the following report:
This is a problem with the interpreter, that is, jvm made a mistake in converting bytecode into machine code. There are many reasons for this, generally jdk bug can be changed to different jvm modes such as-XInt, pure interpretation mode is compiled in the run-time information, you can check who went wrong by excluding compiling these classes to try.
On how to use CrashAnalysis tools to achieve jvm hs_err_pid.log file analysis is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.