05
1/ Verify CPU, I/O overconsumption, and memory leak:
CPU: Check processor load servers with top
I/O: Check I/O with Visual VM
Memory: Check GC activity of differents JVM with Visual VM, JConsole, heap dump, MAT
-> These 3 points are used to identify programming errors leading to excessive consumption of CPU and I / O, the infinite loop and memory-leaks.
2/ Check resources access such as JDBC pool, thread pools or synchronized blocks:
Check the thread number and activity in generating a « Thread Dump » ( « kill -3 <PID> ») bound for running JVM processes.
If you have a JMX access, Visual VM and its plugins can be very helpful to analyze the state of threads and pools size