ThreadDump Analysing

We will analyse the thread dump by taking different scenarios:

1) 

"ExecuteThread: '15' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x01c7fe88 nid=0x20 in Object.wait() [cbfff000..cbfffc28]
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:429)
        at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:153)
        - locked <0xd9925f60> (a weblogic.kernel.ExecuteThread)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)

Here when we seen that object is waited for some other resources, Lets discuss about this in programming when we use synchronized objects for some typical application like blank. This happens because of two or more threads tries to acquires lock on the object(some other thread may hold that)