Benny,
On 2/4/22 11:06, Benny Kannengießer wrote:
Thanks again Mark for the tip!
Like you suggested I wrapped the response, overriding "setStatus()" - but the method didn't get
called because the wrapper is not a subclass of the original response, it's just a façade. I think the
"setStatus()
Thanks again Mark for the tip!
Like you suggested I wrapped the response, overriding "setStatus()" - but the
method didn't get called because the wrapper is not a subclass of the original
response, it's just a façade. I think the "setStatus()" method of the wrapped
response (inner object) was
Hello Alan,
I currently don't have an appropriate setup here, so just the principle method
:.
Use "top - H" or htop to identify the tomcat threads with highest CPU usage.
Write down thread ids.
Create Java stack of tomcat, e. G. use jstack, kill - 3 or
jvisualvm.
Within the stack trace there is
Hello Thomas,
Thanks for your input here, what's your weapon of choice to identify this
thread bar thread dump? I just downloaded jvmtop from github but that didn't
seem to give me any clue at all about independent threads.
Cheers
Alan
-Original Message-
From: Thomas Hoffmann (Speed4T
Hello,
when I encounter high CPU usage, it's best to identify the thread Id which is
eating CPU.
Making a thread dump, you can then search for the thread id within this dump.
This works good for long lasting threads. If the CPU eating thread changes
quickly, it's harder to figure out.
Greeting
