This section describes the notes on monitoring J2EE applications by using Java VisualVM
Table K-1 Functionality provided by Cosminexus Developer's Kit for Java
Item No. | Functionality | Explanation |
---|---|---|
1 | Extended thread dump functionality and extended VerboseGC functionality | Monitoring the Java heap and Perm heap size |
2 | Extended thread dump functionality | Thread information |
3 | javagc command | Execution of FullGC |
Table K-2 Cause of occurrence of garbage collection of the extended verbosegc information
Item No. | Java VisualVM functionality with garbage collection | Cause of the occurrence garbage collection of extended verbosegc information |
---|---|---|
1 | Application monitoring functionality | System.gc |
2 | Application sampling functionality | System.gc |
3 | Application profiling functionality | JVMTIForceGC |
Application (pid-numeric value) |
Writing Java core to full-path-name-of-thread-dump-file...OK |
However, if the Stop standard output option of the extended thread dump is specified in the startup options of the J2EE server and if the J2EE server is started to output the extended thread dump in standard output format, the thread dump can be output to the Main window tab.