Profile Image
vijima17

server went hung state

we have 3 nodes and each has 3 instances , one particular time 2_3,3_3 instances went hung state . what could be the reason


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

    Please Sign In or to post your comment or answer

    Profile Image

    Ram Lakshmanan

    Hello Viji!

     

     There could be several reasons why application is going into hung state. Some of the reasons are:

    • Garbage collection pauses
    • Threads getting BLOCKED
    • Network connectivity
    • Load balancer routing issue
    • Heavy CPU consumption of threads
    • Operating System running with old patches
    • Memory Leak
    • DB not responding properly

    :

    :

     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.

    Got something else on mind? Post Your Question