Full gc found very frequently in the project. It reached 13 times per minute. I suspect there may be a memory leak. So in the night to find information on memory leaks.
Long-term memory footprint and lead to system instability in general there are two possibilities:
1. a large number of objects are created and cached before the release there are a lot of old objects new object is created so that high long-term memory footprint.
- As follows: memory continue to be consumed at a high level it is difficult to return to the low, a large number of objects in constant creation, after a very long period of time and then be recycled. For example: in the HttpSession save a lot of paging query data, and HttpSession session timeout is too long (for example: one day), then there are a lot of new objects produced the next day before the release of old objects.
- The solution: a shared pool of objects can be used for caching mechanism to prevent their creation; the temporary cache object should be released in time; Another approach is to expand the system memory capacity.
2. In other cases, a memory leak problem
- As follows: rising low memory recovery point (the lowest point of each memory recovery even in a straight line, then it is a rising line); the frequency of garbage collection higher and higher, higher and higher memory footprint, culminating in "Out of Memory Exception" system abnormalities.
- Solution: locate those classes or objects have memory leaks and revise and improve these classes to avoid memory leaks. The method is: After a period of testing, monitoring, if the number of objects of a class record highs, even after the number of the JVM Full GC still do not fall down, these objects are basically belong to the object memory leaks.
Then we would use Jconsole to monitor the weblogic jvm.
Since jconsole and weblogic windows are on the same machine, the configuration of the following steps:
1. The first is to configure WebLogic startup script.
D:\weblogic\domains\cebbch_domain\bin\startWebLogic.cmd
In which to find
After set JAVA_OPTIONS =% SAVE_JAVA_OPTIONS%, adding a word, becomes:
set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% -Dcom.sun.management.jmxremote
2. Locate the weblogic console
Domain> Security> Enable anonymous administrators to find and hook on the front of the grid
3. Then start jconsole, find weblogic server's process ID, you can connect a success. Otherwise, the only connection sun.tools.jconsole.Jconsole.
So far, jconsole already successfully connected the weblogic.
Reproduced in: https: //www.cnblogs.com/villadom/p/3973442.html