31 lines
829 B
Plaintext
31 lines
829 B
Plaintext
|
OK: JVM diagnostics collected for PID 1234
|
||
|
|
|
||
|
|
Detected JVM process:
|
||
|
|
PID USER RSS_MB CPU COMMAND
|
||
|
|
1234 app 2048 42.1 java -Xms2g -Xmx2g -jar order-api.jar
|
||
|
|
Thread count: 188
|
||
|
|
|
||
|
|
Heap and JVM evidence:
|
||
|
|
|
||
|
|
[jcmd VM.flags]
|
||
|
|
1234:
|
||
|
|
-XX:InitialHeapSize=2147483648 -XX:MaxHeapSize=2147483648
|
||
|
|
|
||
|
|
[jcmd GC.heap_info]
|
||
|
|
garbage-first heap total 2097152K, used 1521000K
|
||
|
|
|
||
|
|
[jcmd Thread.print summary]
|
||
|
|
102 java.lang.Thread.State: WAITING
|
||
|
|
53 java.lang.Thread.State: RUNNABLE
|
||
|
|
33 java.lang.Thread.State: TIMED_WAITING
|
||
|
|
|
||
|
|
Evidence:
|
||
|
|
PID=1234 thread_count=188 top=10
|
||
|
|
|
||
|
|
Recommended next steps:
|
||
|
|
- Review GC logs and recent application errors
|
||
|
|
- Check JVM heap sizing against container or host memory limits
|
||
|
|
- Check thread count trend in monitoring before concluding a leak
|
||
|
|
- Capture jstack only if approved by operational process
|
||
|
|
- Attach this output to incident ticket
|