Shulou(Shulou.com)06/02 Report--

This article mainly analyzes the relevant knowledge points of jvm crash case analysis, the content is detailed and easy to understand, the operation details are reasonable, and has a certain reference value. If you are interested, you might as well follow the editor to have a look, and follow the editor to learn more about the case analysis of jvm crash.

Over the past half a month, the reliability of the new web server has declined sharply, mainly due to jvm crash. The causes of jvm crash are also related to java GC (Garbage Collection).

Checked sun's document "Trouble-Shooting and."

"Diagnostic Guide", finally have some preliminary understanding. Check the 4 documents at the time of jvm crash (hs_err_pidXXXX) for exactly the same reason:

An unexpected error has been detected by HotSpot Virtual Machine:

#

# SIGSEGV (0xb) at pc=0x010d2d9e, pid=8089, tid=5417904

#

# Java VM: Java HotSpot (TM) Server VM (1.5.0_07-b03 mixed mode)

# Problematic frame:

# V [libjvm.so+0x3efd9e]...

Then check the documents of jboss, and preliminarily determine that the cause of jvm crash is caused by insufficient permsize. Because the system uses a lot of spring beans,jvm, it needs to use Permanent Generation Heap to store reflective data.

The solution is to add-XX:MaxPermSize=128m,jdk5.0 to JAVA_OPTS, the default initial value is 8Mb (client) / 16Mb (server), and the maximum value is 64Mb.

Now Perm Generation only uses 68%, while the previous four jvm crashes, the value is 99%.

It remains to be seen whether the availability of the new server will be resolved as a result.

On the "case analysis of jvm crash" is introduced here, more related content can be searched for previous articles, hope to help you answer questions, please support the website!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.