JVM (Java Virtual Machine) memory leakage automatic-detection method and system

Abstract

The invention discloses a JVM (Java Virtual Machine) memory leakage automatic-detection method and system. The method include: S1, setting a collection use-amount threshold value of memory on the basis of acquired memory pool management objects, and registering a listener on the basis of an acquired memory system management object; S2, informing the listener of current memory information by the memory system management object if the memory exceeds the collection use-amount threshold value after a JVM completes garbage collection (GC); and S3, analyzing the current memory information by the listener on the basis of maximum memory use-amount rising frequency and a last memory use amount to judge whether memory leakage exists. According to the method, the JVM memory use information can be automatically acquired, the memory use information of the JVM can be acquired in a more timely manner after GC completion, the accurate memory information is obtained without the need for external connection or instruction calling, and normal running of programs is not impacted; and further, when it is determined that memory leakage exists, alarming is triggered, thus a system maintainer is informedof possible existence of a system memory problem in advance, and an effect of locating the problem as early as possible is facilitated.

Description

technical field [0001] The invention relates to the field of computers, in particular to a JVM memory leak automatic detection method and system. Background technique [0002] JVM (Java Virtual Machine, Java Virtual Machine), as the execution environment of Java programs, has its own set of memory management mechanisms, which can complete allocation and reclaim memory. For Java programmers, there is no need to care too much about how objects are stored and used in memory, because there is a garbage collection (Garbage Collection, GC for short) mechanism that ensures the normal operation of Java programs. However, even a tested program may cause JVM memory leaks or memory overflows due to improper code writing or object use. It is also possible that the memory configuration of the JVM is unreasonable and cannot meet the needs of program operation (such as a large number of concurrent requests), resulting in insufficient memory. Although this situation is not a memory leak, t...

AI Technical Summary

Problems solved by technology

[0005] 1) Manual operation is required, and manual continuous monitoring is required to observe the results after JVM GC, and the degree of automation is low

[0006] 2) The obtained JVM memory information is not the JVM memory status just after GC (garbage collection), and there may be misjudgment of memory changes

[0007] 3) It is not safe and convenient to establish a connection or call the running JVM through instructions. At the same time, for some systems with high real-time requirements and a large number of concurrent requests, real-time statistics of the number of objects will seriously affect the normal operation of the system

Images