HI, we have this message (the response of fastthread.io):
Our machine learning (ML) algorithms have detected problems in your application which can cause application unresponsiveness. Below are the problems detected by our ML algorithms:
9 threads are BLOCKED on line #43 of weblogic.cluster.StateDumpMessage file in writeExternal() method. If threads are BLOCKED for a prolonged period, your application may become unresponsive. Examine their stack trace.
6 threads are in RUNNABLE state and they all have same stack trace. If your application's CPU consumption is high, it's caused because of this stack trace.
'[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'' thread is stuck on getDeclaredConstructors0() method in java.lang.Class file. Before getting stuck, this thread obtained 2 locks (weblogic.ejb.container.internal.AggregatableOpaqueReference lock, java.util.ArrayList lock) and never released it. Due to that 9 threads are BLOCKED as shown in this stack trace. If threads are BLOCKED for a prolonged period, your application can become unresponsive.
View(s)
0 Share(s)
Facebook
Twitter
Email
Copy Link
Hello Tecnologia!
The report URL you had given in this description has differen error message from the error messages you have reported in your description. I assume you have enclosed different report. But keeping it aside.
From your description, we can see fastThread pointing out 3 problems in your application. Why don't click on the stacktraces hyperlink given in those error message. It will point out the lines of code that is causing the performance problems in your application.
Edit your Comment