Question

我注意到有一些 st子。

I like to check what could be the cause of the stuck thread just base on the thread dump logs below. Any advise anyone? And also what is the difference between a fat lock and a thin lock?

        "[STUCK] ExecuteThread:  25  for queue:  weblogic.kernel.Default (self-tuning) " id=87495 idx=0x274 tid=15308 prio=1 alive, in native, blocked, daemon

            -- Blocked trying to get lock: com/jnn/testController@0x135a26c0[thin lock]

Answer 1

单单靠一堆read子就赢得了太大的帮助,无法从根本上解决问题。在每秒5秒的间隔间进行4或5套校对堆放场。最终,您将拥有一份单一的记录文件,在服务器上拥有大约20至25秒,值得采取行动。

Then you should look for you want to check is a stuck thread or long running transaction is happening, all the thread dumps will show a certain thread id is at the same line in your java stack trace. In simpler terms, the transaction (say in an EJB or database) is spanning across multiple thread dumps and hence needs more investigation.

现在你通过Samurai 或TDA(I hasnt used TDA本人)来管理这些节目时,它将在红彩色中强调这些内容,以便你能够迅速点击,进入显示问题的线。

See an example of this here。看看Samurai在这方面的产出形象。绿色罚款。红色和灰色需要研究。

在你的案件中,有25条read被阻断,试图在物体上lock锁。

com/jnn/testController@0x135a26c0

搜查其余锁,看看同一物体的锁,看看它为什么没有释放锁——这在锁的痕迹中就会看到。

Answer 2

A "thin lock" is a lock with no contention (contention happens when a thread has to wait before acquiring a lock). Thin locks get promoted to "Fat locks" when there is contention and a list is made with all threads waiting to acquire the lock.

You can read more on the argument here: http://download.oracle.com/docs/cd/E13150_01/jrockit_jvm/jrockit/geninfo/diagnos/thread_basics.html

友情链接