Profile Image
Pedro Llanten

Review request

Dear community, based on your experience, is it possible to determine if the slowness experienced in our portal during the time these dumps were taken is due to some of our application or some external attack?

Stay tuned to your comments.
Thank you.


Report URL - https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMjQvMDQvMTcvdGhyZWFkX2R1bXBzLnppcC0tMjAtNy0zMw==

    Please Sign In or to post your comment or answer

    Profile Image

    Ram Lakshmanan

    Hello Pedro!

     

     I reviewed your threads dump that were captured every 10 seconds from 13:28:08 to 13:35:05. I don't see any major problems in these thread dumps. However slowness in your application can happen because of various reasons:

    • Garbage collection pauses (high chance)
    • Network connectivity
    • Load balancer routing issue
    • Heavy CPU consumption of threads
    • Operating System running with old patches
    • Memory Leak
    • DB not responding properly
    • Kernel issues
    • Backend slow downs
    • Hypervisor/container orchestrator not allocating enough resources

    :

    :

     

     So just thread dump is not enough to diagnose the problem. 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/artifacts to do thorough analysis.

     

     You can use the open source yCrash script which will capture 360-degree application level artifacts (like GC logs, 3 snapshots of thread dumps, heap dumps) and system level artifacts (like top, top -H, netstat, vmstat, iostat, dmesg, diskusage, kernel parameters...). Once you have these data, either you can manually analyze them or upload it to yCrash tool, which will analyze all these artifacts and generate root cause analysis report. It has potential to indicate the root cause of the problem.

    Profile Image

    Mahesh

    Hi Pedro,

     

    According to the fastThread report, it appears that 10 threads are currently stuck in your application. This may be the cause of the slowdown you're experiencing. If I am not wrong, your application uses JGroup for messaging. It seems that your application is encountering a delay in receiving a response from the JGroup service. As long as your application hasn't finished reading the response data, its threads will remain stuck in the java.net.SocketInputStream.socketRead0() API.

     

    You can review all 10 stuck threads by following the link below:

     

    https://fastthread.io/same-state-threads.jsp?state=BAD&m=amF2YS5uZXQuU29ja2V0SW5wdXRTdHJlYW0uc29ja2V0UmVhZDAoTmF0aXZlIE1ldGhvZCk=&pc=1&ts=2024-04-18T08-29-16

    Got something else on mind? Post Your Question