Hello Lucas!
Greetings. Here are some quick observations, I would like to share.
a. Your application is using Log4j framework. Log4j framework has reached end of life on Aug' 2015. It has several performance problems. I could see 15 threads (originating from your tomcat container) stuck in Log4j logging. Log4j framework has several performance problems. Below are those 15 stuck threads stack trace. This may cause unresponsiveness in your application.
Here is a similar log4j problem faced by another customer. You should consider upgrading to Log4j2 framework (or something similar).
b. There is a good chance that log4j might be causing unresponsiveness in your application. But however it's hard to confirm with the data shared captured. You have captured only thread dump, that too one snapshot of it. It's always a good practice to capture 3 thread dumps in a gap of 10 seconds between each one. Besides thread dumps you might have to capture other logs to do thorough analysis. You may consider using tools like yCrash, which would captures application level logs (like GC logs, 3 snapshots of thread dumps, heap dumps) and system level logs (like top, top -H, netstat, vmstat, iostat, dmesg, diskusage...) and does complete analysis to identify the root cause of the problem.
Edit your Comment