Troubleshooting ideas:
1, first find high CPU-intensive process PID top command
2, top -H -p <PID> to see which occupy high CPU threads XCID
3, jstack <PID> /home/aaa.log the stack information is stored in a file, the file download
4, step two of the thread ID, converted to hexadecimal, search aaa.log in, you can see the call stack for this thread