weblogic挂起，trace原因分析。
<Feb 6, 2018 10:25:21 AM CST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '17' for queue: 'weblogic.kernel.Default' has been busy for "1,628" seconds working on the request "Http Request: /BOCWebServices/BusinessObjectControler", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.><Feb 6, 2018 10:25:21 AM CST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '18' for queue: 'weblogic.kernel.Default' has been busy for "1,646" seconds working on the request "Http Request: /BOCWebServices/BusinessObjectControler", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
<Feb 6, 2018 10:25:21 AM CST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '19' for queue: 'weblogic.kernel.Default' has been busy for "1,638" seconds working on the request "Http Request: /BOCWebServices/BusinessObjectControler", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
<Feb 6, 2018 10:25:21 AM CST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '22' for queue: 'weblogic.kernel.Default' has been busy for "1,716" seconds working on the request "Http Request: /BOCWebServices/BusinessObjectControler", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
<Feb 6, 2018 10:25:21 AM CST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '23' for queue: 'weblogic.kernel.Default' has been busy for "1,703" seconds working on the request "Http Request: /BOCWebServices/BusinessObjectControler", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
<Feb 6, 2018 10:25:21 AM CST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '24' for queue: 'weblogic.kernel.Default' has been busy for "1,752" seconds working on the request "Http Request: /BOCWebServices/BusinessObjectControler", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
===== FULL THREAD DUMP ===============
Tue Feb6 17:38:57 2018
BEA JRockit(R) R26.3.0-32_CR283061-63465-1.4.2_10-20060620-1808-linux-ia32
"Main Thread" id=1 idx=0x2 tid=11261 prio=5 alive, in native, waiting
-- Waiting for notification on: weblogic/t3/srvr/T3Srvr@0x4a790a48
at jrockit/vm/Threads.waitForSignal(J)Z(Native Method)
at jrockit/vm/Locks.wait(Ljava/lang/Object;J)V(Unknown Source)
at java/lang/Object.wait()V(Native Method)
at weblogic/t3/srvr/T3Srvr.waitForDeath()V(T3Srvr.java:1207)
^-- Lock released while waiting: weblogic/t3/srvr/T3Srvr@0x4a790a48
at weblogic/t3/srvr/T3Srvr.run([Ljava/lang/String;)I(T3Srvr.java:389)
at weblogic/Server.main([Ljava/lang/String;)V(Server.java:32)
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
-- end of trace
"(Signal Handler)" id=2 idx=0x4 tid=11263 prio=5 alive, in native, daemon
"(Code Generation Thread 1)" id=3 idx=0x6 tid=11264 prio=5 alive, in native, native_waiting, daemon
"(Code Optimization Thread 1)" id=4 idx=0x8 tid=11265 prio=5 alive, in native, native_waiting, daemon
"(GC Main Thread)" id=5 idx=0xa tid=11266 prio=5 alive, in native, daemon
"(GC Worker Thread 1)" id=? idx=0xc tid=11267 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 2)" id=? idx=0xe tid=11268 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 3)" id=? idx=0x10 tid=11269 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 4)" id=? idx=0x12 tid=11270 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 5)" id=? idx=0x14 tid=11271 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 6)" id=? idx=0x16 tid=11272 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 7)" id=? idx=0x18 tid=11273 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 8)" id=? idx=0x1a tid=11274 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 9)" id=? idx=0x1c tid=11275 prio=5 alive, native_waiting, daemon
"(GC Worker Thread 10)" id=? idx=0x1e tid=11276 prio=5 alive, native_waiting, daemon
"(VM Periodic Task)" id=6 idx=0x20 tid=11277 prio=10 alive, in native, daemon 从操作系统可以看出 线程11277占用了很高的cpu资源，
"Finalizer" id=7 idx=0x22 tid=11278 prio=8 alive, in native, native_waiting, daemon
at jrockit/memory/Finalizer.getPendingFinalizee(Z)Ljava/lang/Object;(Native Method)
at jrockit/memory/Finalizer.access$100(Z)Ljava/lang/Object;(Unknown Source)
at jrockit/memory/Finalizer$4.run()V(Unknown Source)
at java/lang/Thread.run()V(Unknown Source)
at jrockit/vm/RNI.c2java(IIII)V(Native Method)
-- end of trace
"Reference Handler" id=8 idx=0x24 tid=11279 prio=10 alive, in native, native_waiting, daemon
at java/lang/ref/Reference.getPending()Ljava/lang/ref/Reference;(Native Method)
at java/lang/ref/Reference.access$000()Ljava/lang/ref/Reference;(Unknown Source)
。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。
Open lock chains
================
Chain 1:
"ExecuteThread: '0' for queue: 'weblogic.kernel.Default'" id=11 idx=0x28 tid=11281 waiting for weblogic/ejb20/pool/StatelessSessionPool@0x4bc13cf8 held by:
"ExecuteThread: '1' for queue: 'weblogic.kernel.Default'" id=12 idx=0x2a tid=11282 (active)
Chain 2:
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=45 idx=0x6c tid=11315 waiting for java/lang/String@0x4aeffb90 held by:
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" id=43 idx=0x68 tid=11313 (active)
===== END OF THREAD DUMP ===============
请教大家这个应该从哪些地方着手分析，这里是发生死锁了吗？是在挣用哪一个资源呢？
页:
[1]