Java application memory leak analysis on the AIX platform based on IBM JDK

Java developers generally do not need to consider the issue of memory release, all the GC to deal with. However, in some production environments, the JVM has been running for a long time, even some small, http://www.aliyun.com/zixun/aggregation/36295.html Java objects, which can lead to exhaustion of memory resources, and ultimately the problem of application crashes. This article will lead the reader to understand the Java application memory leak survey method based on the IBM JDK and analyze the ideas on an AIX platform based on the actual case analysis process of Java application memory depletion.

The first step is to determine whether a memory leak problem

Based on the error log in the production environment and GC log files, make a preliminary assessment of whether it is a memory leak problem.

Error log for Java application:

The available memory is judged in the application, and the WARNING log is exported when the available memory is low.

Use IBM pattern modeling and Analysis Tools for Java garbage Collector to analyze GC logs.

Figure 1. Select the GC log file to open the IBM JDK


Figure 2. Click Graph View Part Display


Figure 3. Show GC analysis diagram

The use of the Java memory heap (HEAP) is seen in the graph as a persistent upward trend.

From this we can conclude that the Java application has a memory leak problem, resulting in the memory heap is not released.