thread dumps

Hello

Can we take dumps of thread for Jboss Application server by using Big Brother, if so please let me know how we can move forward.

Thanks, in advance

Yogesh

you will need to write your own external script that I can not find specific scripts Jboss on http://www.deadcat.net or Google search. There is a reference to bb-check - jboss.sh when searching on Google but I can not find the script. (He mentioned in the documentation of Collabnet and it does not mean that it does what you want)

Tags: Dell Tech

Similar Questions

How should I interpret java thread dumps?

I have a multi-threaded application, I am running on a BlackBerry 9000. I suspect there are blocking issues.

I figured out how to trigger the trace of the stack using javaloader - usb logstacktraces (rather than wait for the alert for error "not responding") and can fetch using javaloader - usb eventlog, but I cannot interpret them.

When I develop java applications normal can I use ^-to get a thread dump containing the source files, line numbers, and (most importantly) a list of locks and blocks, telling me that has a lock on an object, and which is blocked waiting for a lock to be released (either by calling the wait() method or exit).

I don't know if this information is in the Blackberry stack traces.
```
guid:0x9C3CD62E3320B498 time: Thu Sep 10 15:51:37 2009  severity:0 type:3 app:Java Exception data:
    ForcedStackTraceException
    baconology(160) 33 2 0x482E4000
    baconology(4AA957F5)
     BlockRun
     nap
     0x3EF
    baconology(4AA957F5)
     BlockRun
     waitForBuffer
     0x4BF
    baconology(4AA957F5)
     PiecewiseSourceStream
     read_
     0x14D7
    baconology(4AA957F5)
     PiecewiseSourceStream
     read
     0x1570
    net_rim_cldc-16(4A739706)
     DataSourceInputStream
     read
     0x25AF
    net_rim_media(4A739765)
     MP4Info
     
     0x34E1
    net_rim_media(4A739765)
     MP4Info
     
     0x2DA7
    net_rim_media(4A739765)
     MP4Info
     
     0x2D63
    net_rim_media(4A739765)
     MP4Info
     
     0x33A8
    net_rim_media(4A739765)
     StreamingMediaPlayer
     doRealize
     0x9224
    net_rim_cldc-16(4A739706)
     BasicPlayerImpl
     realize
     0xF80
    baconology(4AA957F5)
     JMFToy
     fabricateAndRealizePlayer
     0x9F5
    baconology(4AA957F5)
     JMFToy$3
     run
     0xD94
    net_rim_cldc-1(4A739706)
     Thread
     run
```
Given that this thread is blocked waiting to enter the BlockRun.nap () call, I can assume that it is blocked, waiting for a lock on * this *, because otherwise it would be inside the Object.wait () function, waiting for another thread to issue a notifyAll().

What I need to know is the thread that has the lock, so I can arrange for to be released or not granted at all.

Each (single-threaded) stack trace begins with the name of the process that owns the thread, followed by the ID process in parentheses, then by the thread ID, then the State of the thread (1 = RUNNABLE, 2 = pending, 3 = TIMED WAITING, 4 = BLOCKED), then the ID of the lock on which thread executes a wait(), or the ID of the lock, the thread is stuck on (waiting to acquire).

After the stack traces there is a list of the locks. The list shows which own threads which locks and locks Java class names.

The information contained in the stack traces and the list of locks is sufficient for an automated tool to analyze the dependencies between threads and also find dead-locks (as appropriate). I depeloped such a tool (thus, it is possible, and it's not hard to do), but I'm not free to release him.

Collect the Thread Dump using Script and live in the separate log file
Legends of dear,

I ask you to provide me with a few lines of useful guide to collect the Thread Dump using script on linux and redirect the output to a separate log file, but not the STDOUT file. If it is redirect to STDOUT then how to extract only the thread stack to a separate log file.

I used
ps - ef | grep java
kill - 3 < pid > > > ss1_td.log

but it does not provide the thread stack to the log file.

Any aid operation would be appreciated a lot.

Kind regards
Knockaert
Karthik,

Please see this link below

http://www.industryvertical.co.in/2013/01/script-thread-dump-of-multiple-servers.html

site of my friend where we placed a hands-on experience.

Mark this if useful for you

Kind regards

Bouchra Arun.

How to get lots of thread dump without killing-3?
I am trying to solve a problem of thread blocked involving multiple threads external middleware, it blocks what locks being help in the middleware client libraries. Unfortunately in the environment, most people (including those available at 2:00 when offshore is testing) have access to Linux for the JVM WebLogic user ID, so they cannot issue a kill-3.

Thread through the console (and WLST) dumps are not enough, because they are not full thread dumps, that is, they do not show what threads hold locks (they show only what are threads waiting for locks) - that is, they contain no lines like:

-locked (an oracle.jdbc.driver.T4CConnection) < 0x0000000798fc9e88 >

Is it possible to achieve this programmatically or otherwise, far from being able to issue a sigquit (kill-3) to the same user WebLogic runs under?

WebLogic 10.3.5, Sun/Oracle Java 1.6.0_33 (64-bit) 5.6 RHEL. And, FWIW, SonicMQ 8.5 - our threads WebLogic are apparently stuck trying to write off of a TX of XA.
Hi Steve,.

There is a WebLogic Admin command to take dump thread. It is obsolete, but you can still use it.

Reference http://docs.oracle.com/cd/E13222_01/wls/docs81/admin_ref/cli19.html

Thank you

Laurent Mathieu

Thread Dump Oracle Service Bus
Hi all

I'm new to the SOA world. I tried my hands on the OSB.

I don't know what is the cause?

= FULL THREAD DUMP =.
Kill Mar 27 16:24:29 2012
BEA JRockit (R) R27.6.1-20-104573-1.6.0_05-20081016-1236-linux-ia32

"Main Thread" id = 1 idx = 0 x 4 tid = 28283 prio = 5 alive, natively, waiting
[- Awaiting notification on: locking of weblogic/t3/srvr/T3Srvr@0x10533378[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to java/lang/Object.wait (J) V (Native Method)
to java/lang/Object.wait(Object.java:485)
to weblogic/t3/srvr/T3Srvr.waitForDeath(T3Srvr.java:811)
[^ - Lock released pending: weblogic/t3/srvr/T3Srvr@0x10533378[fat lock]
to weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:459)
to weblogic/Server.main(Server.java:67)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"(Manager of signals)" id = 2 idx = 0 x 8 tid = 28284 prio = 5 alive, natively, demon

"(GC hand Thread)" id = 3 idx = 0xc tid = 28285 prio = 5 living, native, native_waiting, demon

"(GC Worker Thread 1)" id =? IDX = 0 x 10 tid = 28286 prio = 5 alive, natively, demon

"(GC Worker Thread 2)" id =? IDX = 0 x 14 tid = 28287 prio = 5 alive, natively, demon

"(GC Worker Thread 3)" id =? IDX = 0 x 18 tid = 28288 prio = 5 alive, natively, demon

"(GC working Thread 4)" id =? IDX = 0x1c tid = 28289 prio = 5 alive, natively, demon

"(Code Generation 1 wire)" id = 4 idx = 0 x 20 tid = 28292 prio = 5 living, native, native_waiting, demon

ID '(code optimization Thread 1)' = 5 idx = 0 x 24 tid = 28293 prio = 5 living, native, native_waiting, demon

ID "(tâche périodique de VM) ' 6 = idx = 0 x 28 = 28294 prio = 10 tid living, native, demon"

'Finalizer' ID = 7 idx = 0x2c tid = 28295 prio = 8 living, native, native_waiting, demon
to jrockit/memory/Finalizer.waitForFinalizees ([Ljava/lang/object ;) I (Native Method)])
to jrockit/memory/Finalizer.access$500(Finalizer.java:12)
to jrockit/memory/Finalizer$4.run(Finalizer.java:159)
to java/lang/Thread.run(Thread.java:619)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"Reference Manager" id = 8 idx = 0 x 30 = 28296 prio = 10 tid living, native, native_waiting, demon
at java/lang/ref/Reference.waitForActivatedQueue () Ljava/lang/ref/reference; (Native Method)
to java/lang/ref/Reference.access$100(Reference.java:11)
to java/lang/ref/Reference$ReferenceHandler.run(Reference.java:79)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"(Capteur événement Thread)" id = 9 idx = 0 x 34 tid = 28297 prio = 5 alive, natively, demon "

ID = 12 "Timer-0" idx = 0 x 38 tid = 28309 prio = 5 living, native, waiting, demon
[- Awaiting notification on: locking of java/util/TaskQueue@0x10159ef8[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
java/lang/Object.wait (J) V (Native Method) [reduced]
to java/util/TimerThread.mainLoop(Timer.java:509)
[^ - Lock released pending: java/util/TaskQueue@0x10159ef8[fat lock]
to java/util/TimerThread.run(Timer.java:462)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"Timer 1" id = 13 idx = 0x3c tid = 28374 prio = 5 living, native, waiting, demon
[- Awaiting notification on: locking of java/util/TaskQueue@0x8f34020[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
java/lang/Object.wait (J) V (Native Method) [reduced]
to java/util/TimerThread.mainLoop(Timer.java:509)
[^ - Lock released pending: java/util/TaskQueue@0x8f34020[fat lock]
to java/util/TimerThread.run(Timer.java:462)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"ExecuteThread [ASSET]: '0' for the queue:"weblogic.kernel.Default (self-adjusting)"" id = 14 idx = 0 x 40 = 28375 prio = 5 tid living, native, waiting, demon
[- Awaiting notification on: locking of weblogic/work/ExecuteThread@0x8f34b50[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to jrockit/vm/Locks.wait(Locks.java:2250) [Inline]
to java/lang/Object.wait(Object.java:485) [Inline]
in weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157) [optimised]
[^ - Lock released pending: weblogic/work/ExecuteThread@0x8f34b50[fat lock]
to weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"weblogic.time.TimeEventGenerator" id = 15 idx = 0 x 44 tid = 28379 prio = 9 living, native, waiting, demon
[- Awaiting notification on: locking of weblogic/time/common/internal/TimeTable@0x8f50188[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
java/lang/Object.wait (J) V (Native Method) [reduced]
to weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
[^ - Lock released pending: weblogic/time/common/internal/TimeTable@0x8f50188[fat lock]
to weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)
to java/lang/Thread.run(Thread.java:619)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"JMAPI event thread" id = 16 idx = 0 x 48 tid = 28380 prio = 5 living, native, native_waiting, demon

"weblogic.timers.TimerThread" id = 17 idx = 0x4c tid = 28381 prio = 9 living, native, waiting, demon
[- Awaiting notification on: locking of weblogic/timers/internal/TimerThread@0x8f594f8[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
java/lang/Object.wait (J) V (Native Method) [reduced]
to weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:267)
[^ - Lock released pending: weblogic/timers/internal/TimerThread@0x8f594f8[fat lock]
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"ExecuteThread [ASSET]: '1' for the queue:"weblogic.kernel.Default (self-adjusting)"" id = 18 idx = 0 x 50 = 28385 prio = 5 tid living, native, waiting, demon
[- Awaiting notification on: locking of weblogic/work/ExecuteThread@0x8f5d040[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to jrockit/vm/Locks.wait(Locks.java:2250) [Inline]
to java/lang/Object.wait(Object.java:485) [Inline]
in weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157) [optimised]
[^ - Lock released pending: weblogic/work/ExecuteThread@0x8f5d040[fat lock]
to weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

21-id = "Timer 2" idx = 0 x 54 tid = 28386 prio = 5 living, native, waiting, demon
[- Awaiting notification on: locking of java/util/TaskQueue@0x8f6d748[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
java/lang/Object.wait (J) V (Native Method) [reduced]
to java/util/TimerThread.mainLoop(Timer.java:509)
[^ - Lock released pending: java/util/TaskQueue@0x8f6d748[fat lock]
to java/util/TimerThread.run(Timer.java:462)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"Thread-8" id = 22 idx = 0 x 58 tid = 28387 prio = 5 living, native, parking, daemon
-Parking to wait: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0xff98b00
to jrockit/vm/Locks.park0 (J) V (Native Method)
to jrockit/vm/Locks.park(Locks.java:2506)
to sun/misc/Unsafe.park (ZJ) V (Native Method)
to java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
to java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
to java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
to weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
to weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
to weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:615)
to weblogic/store/internal/PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

' ExecuteThread: '0' for the queue: 'weblogic.socket.Muxer' "id = 23 idx = 0x5c tid = 28388 prio = 5 alive, natively, blocked, daemon
[- Blocked trying to be locking: lock java/lang/String@0xffb5b88[fat]
at jrockit/vm/Threads.waitForUnblockSignal () V (Native Method)
to jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1674) [Inline]
in jrockit/vm/Locks.fatLockReacquire(Locks.java:1912) [optimised]
in jrockit/vm/Locks.lockFat(Locks.java:1780) [optimised]
in jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1311) [optimised]
in jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1258) [optimised]
in jrockit/vm/Locks.monitorEnter(Locks.java:2455) [optimised]
to weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:153)
to weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
to weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
to weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
to weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

' ExecuteThread: '1' for the queue: 'weblogic.socket.Muxer' "id = 24 idx = 0 x 60 tid = 28389 prio = 5 alive, natively, demon
jrockit/ext/epoll/EPoll.epollWait0 (IIII) I have (Native Method)
to jrockit/ext/epoll/EPoll.epollWait(EPoll.java:103)
to weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:156)
[^ - Holding lock: lock of java/lang/String@0xffb5b88[fat]
to weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
to weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
to weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
to weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

' ExecuteThread: '2' for the queue: 'weblogic.socket.Muxer' "id = 25 idx = 0 x 64 tid = 28390 prio = 5 alive, natively, blocked, daemon
[- Blocked trying to be locking: lock java/lang/String@0xffb5b88[fat]
at jrockit/vm/Threads.waitForUnblockSignal () V (Native Method)
in jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1674) [optimised]
in jrockit/vm/Locks.lockFat(Locks.java:1775) [optimised]
in jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1311) [optimised]
in jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1258) [optimised]
in jrockit/vm/Locks.monitorEnter(Locks.java:2455) [optimised]
to weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:153)
to weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
to weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
to weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
to weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

' ExecuteThread: '3' for the queue: 'weblogic.socket.Muxer' "id = 26 idx = 0 x 68 tid = 28391 prio = 5 alive, natively, blocked, daemon
[- Blocked trying to be locking: lock java/lang/String@0xffb5b88[fat]
at jrockit/vm/Threads.waitForUnblockSignal () V (Native Method)
in jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1674) [optimised]
in jrockit/vm/Locks.lockFat(Locks.java:1775) [optimised]
in jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1311) [optimised]
in jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1258) [optimised]
in jrockit/vm/Locks.monitorEnter(Locks.java:2455) [optimised]
to weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:153)
to weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
to weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
to weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
to weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

' ExecuteThread: '4' for the queue: 'weblogic.socket.Muxer' "id = 27 idx = 0x6c tid = 28392 prio = 5 alive, natively, blocked, daemon
[- Blocked trying to be locking: lock java/lang/String@0xffb5b88[fat]
at jrockit/vm/Threads.waitForUnblockSignal () V (Native Method)
in jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1674) [optimised]
in jrockit/vm/Locks.lockFat(Locks.java:1775) [optimised]
in jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1311) [optimised]
in jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1258) [optimised]
in jrockit/vm/Locks.monitorEnter(Locks.java:2455) [optimised]
to weblogic/socket/EPollSocketMuxer.processSockets(EPollSocketMuxer.java:153)
to weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)
to weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)
to weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)
to weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"VDE Transaction processor Thread" id = 30 idx = 0 x 70 tid = 28397 prio = 2 alive, native, waiting, demon
[- Awaiting notification on: locking of com/octetstring/vde/backend/standard/TransactionProcessor@0xff84350[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to java/lang/Object.wait (J) V (Native Method)
to java/lang/Object.wait(Object.java:485)
to com/octetstring/vde/backend/standard/TransactionProcessor.waitChange(TransactionProcessor.java:367)
[^ - Lock released pending: com/octetstring/vde/backend/standard/TransactionProcessor@0xff84350[fat lock]
to com/octetstring/vde/backend/standard/TransactionProcessor.run(TransactionProcessor.java:212)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"DoSManager" id = 33 idx = 0 x 78 tid = 28401 prio = 6 alive, natively, sleep, native_waiting, demon
to java/lang/Thread.sleep (J) V (Native Method)
to com/octetstring/vde/DoSManager.run(DoSManager.java:433)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"OracleTimeoutPollingThread" id = 34 idx = 0x7c tid = 28478 prio = 10 alive, natively, sleep, native_waiting, demon
to java/lang/Thread.sleep (J) V (Native Method)
to oracle/jdbc/driver/OracleTimeoutPollingThread.run(OracleTimeoutPollingThread.java:150)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"Wire-12" id = 35 idx = 0 x 80 tid = 28492 prio = 5 living, native, parking, daemon
-Parking to wait: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0x18625de8
to jrockit/vm/Locks.park0 (J) V (Native Method)
to jrockit/vm/Locks.park(Locks.java:2506)
to sun/misc/Unsafe.park (ZJ) V (Native Method)
to java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
to java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
to java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
to weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
to weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
to weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:615)
to weblogic/store/internal/PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

'Timer-3' id = 36 idx = 0 x 84 tid = 28503 prio = 5 living, native, waiting, demon
[- Awaiting notification on: locking of java/util/TaskQueue@0x18413578[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
java/lang/Object.wait (J) V (Native Method) [reduced]
to java/util/TimerThread.mainLoop(Timer.java:509)
[^ - Lock released pending: java/util/TaskQueue@0x18413578[fat lock]
to java/util/TimerThread.run(Timer.java:462)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"ExecuteThread [ASSET]: '2' for the queue:"weblogic.kernel.Default (self-adjusting)"" id = 37 idx = 0 x 88 = 28635 prio = 5 tid living, native, waiting, demon
[- Awaiting notification on: locking of weblogic/work/ExecuteThread@0x10b10cc0[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to jrockit/vm/Locks.wait(Locks.java:2250) [Inline]
to java/lang/Object.wait(Object.java:485) [Inline]
in weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157) [optimised]
[^ - Lock released pending: weblogic/work/ExecuteThread@0x10b10cc0[fat lock]
to weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"Thread-14" id = 38 idx = 0x8c tid = 28643 prio = 5 living, native, parking, daemon
-Parking to wait: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0x109acbd8
to jrockit/vm/Locks.park0 (J) V (Native Method)
to jrockit/vm/Locks.park(Locks.java:2506)
to sun/misc/Unsafe.park (ZJ) V (Native Method)
to java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
to java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
to java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
to weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
to weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
to weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:615)
to weblogic/store/internal/PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"ExecuteThread [ASSET]: '3' for queue:"weblogic.kernel.Default (self-adjusting)"" id = 39 idx = 0 x 90 = 28663 prio = 5 tid living, native, waiting, demon
[- Awaiting notification on: locking of weblogic/work/ExecuteThread@0x21bc7c28[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to jrockit/vm/Locks.wait(Locks.java:2250) [Inline]
to java/lang/Object.wait(Object.java:485) [Inline]
in weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157) [optimised]
[^ - Lock released pending: weblogic/work/ExecuteThread@0x21bc7c28[fat lock]
to weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"pool-1-wire-1" id = 40 idx = 0 x 94 tid = 28691 prio = 5 living in native, parked
to jrockit/vm/Locks.park0 (J) V (Native Method)
to jrockit/vm/Locks.park(Locks.java:2506)
to sun/misc/Unsafe.park (ZJ) V (Native Method)
to java/util/concurrent/locks/LockSupport.parkNanos(LockSupport.java:198)
to java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1963)
to java/util/concurrent/DelayQueue.take(DelayQueue.java:164)
to java/util/concurrent/ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:582)
to java/util/concurrent/ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:575)
to java/util/concurrent/ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:946)
to java/util/concurrent/ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:906)
to java/lang/Thread.run(Thread.java:619)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"LDAPConnThread-0 ldap://admin-ryprdsbB.baplc.com:7999" id = 41 idx = 0 x 98 = 28800 prio = 5 tid living, native, demon
to jrockit/net/SocketNativeIO.readBytesPinned (Ljava/io/FileDescriptor; [I (Native Method) BILL)
to jrockit/net/SocketNativeIO.socketRead(SocketNativeIO.java:46)
to java/net/SocketInputStream.socketRead0 (Ljava/io/FileDescriptor; [BILL) I (SocketInputStream.Java)
to java/net/SocketInputStream.read(SocketInputStream.java:129)
to java/io/BufferedInputStream.fill(BufferedInputStream.java:218)
to java/io/BufferedInputStream.read(BufferedInputStream.java:237)
[^ - Holding lock: lock of java/io/BufferedInputStream@0x1a960cd0[biased]
to netscape/ldap/ber/stream/BERElement.getElement(BERElement.java:101)
to netscape/ldap/LDAPConnThread.run(LDAPConnThread.java:538)
to java/lang/Thread.run(Thread.java:619)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"Timer-4" id = 42 idx = 0x9c tid = 28819 prio = 5 living, native, waiting, demon
[- Awaiting notification on: locking of java/util/TaskQueue@0x1a38a930[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to java/lang/Object.wait (J) V (Native Method)
to java/lang/Object.wait(Object.java:485)
to java/util/TimerThread.mainLoop(Timer.java:483)
[^ - Lock released pending: java/util/TaskQueue@0x1a38a930[fat lock]
to java/util/TimerThread.run(Timer.java:462)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"LDAPConnThread-1 ldap://admin-ryprdsbB.baplc.com:7999" id = 43 idx = 0xa0 = 28824 prio = 5 tid living, native, demon
to jrockit/net/SocketNativeIO.readBytesPinned (Ljava/io/FileDescriptor; [I (Native Method) BILL)
to jrockit/net/SocketNativeIO.socketRead(SocketNativeIO.java:46)
to java/net/SocketInputStream.socketRead0 (Ljava/io/FileDescriptor; [BILL) I (SocketInputStream.Java)
to java/net/SocketInputStream.read(SocketInputStream.java:129)
to java/io/BufferedInputStream.fill(BufferedInputStream.java:218)
to java/io/BufferedInputStream.read(BufferedInputStream.java:237)
[^ - Holding lock: lock of java/io/BufferedInputStream@0x16a8f110[biased]
to netscape/ldap/ber/stream/BERElement.getElement(BERElement.java:101)
to netscape/ldap/LDAPConnThread.run(LDAPConnThread.java:538)
to java/lang/Thread.run(Thread.java:619)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"ExecuteThread [ASSET]: '4' for queue:"weblogic.kernel.Default (self-adjusting)"" id = 44 idx = 0xa4 tid = 28844 prio = 5 living, native, waiting, demon
[- Awaiting notification on: locking of weblogic/work/ExecuteThread@0x1efa17c0[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to jrockit/vm/Locks.wait(Locks.java:2250) [Inline]
to java/lang/Object.wait(Object.java:485) [Inline]
in weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157) [optimised]
[^ - Lock released pending: weblogic/work/ExecuteThread@0x1efa17c0[fat lock]
to weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"ExecuteThread [ASSET]: '5' for queue:"weblogic.kernel.Default (self-adjusting)"" id = 45 idx = 0xa8 tid = 28845 prio = 5 living, native, waiting, demon
[- Awaiting notification on: locking of weblogic/work/ExecuteThread@0x1efa2410[fat]
at jrockit/vm/Threads.waitForNotifySignal (object/lang/JLjava ;) Z (Native Method)
to jrockit/vm/Locks.wait(Locks.java:2250) [Inline]
to java/lang/Object.wait(Object.java:485) [Inline]
in weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157) [optimised]
[^ - Lock released pending: weblogic/work/ExecuteThread@0x1efa2410[fat lock]
to weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"Thread-16" id = 46 idx = 0xac tid = 28882 prio = 5 living, native, parking, daemon
-Parking to wait: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0x19e63430
to jrockit/vm/Locks.park0 (J) V (Native Method)
to jrockit/vm/Locks.park(Locks.java:2506)
to sun/misc/Unsafe.park (ZJ) V (Native Method)
to java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
to java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
to com/bea/alsb/alert/TaskCollector.run(TaskCollector.java:59)
to java/lang/Thread.run(Thread.java:619)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace

"pool-3-wire-1" id = 47 idx = 0xb0 tid = 29009 prio = 5 living in native, parked
-Parking to wait: java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject@0x19f2fd58
to jrockit/vm/Locks.park0 (J) V (Native Method)
to jrockit/vm/Locks.park(Locks.java:2506)
to sun/misc/Unsafe.park (ZJ) V (Native Method)
to java/util/concurrent/locks/LockSupport.park(LockSupport.java:158)
to java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
to java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
to java/util/concurrent/ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:946)
to java/util/concurrent/ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:906)
to java/lang/Thread.run(Thread.java:619)
to jrockit/vm/RNI.c2java (IIIII) V (Native Method)
-end of the trace
Hello

Sign on support.oracle.com and look for:
(1) problem: 100% use of the processor because of blocked Threads observed with Apache Xml beans [ID 1307201.1]
(2) NOTE: 977591.1 -Thread blocked problem in Oracle WebLogic Server using Apache XMLBeans v2.3

These two looks like your problem. You probably need to update the library XMLBeans.

Best regards
Karol Muszynski

What ' s a weblogic thread dump format?
Hello

I have a question for thread dump in Weblogic.

When I see this message; java.lang.Thread.State: EXECUTABLE; my understanding is that the thread is running.
Example:
"Connection TCP RMI 3025 - 10.30.73.39"-wire t@278
java.lang.Thread.State: EXECUTABLE
at java.net.SocketInputStream.socketRead0 (Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
-locked < 235738ef > (a java.io.BufferedInputStream)
== > this thread runs and reads data...

Now, what is a '[ACTIVE]' thread in Weblogic? my opinion is that it is also a running thread. Am I wrong?

If both threads are running, why one is not also maraked as "[ACTIVE] '?

Another question, what ' s the difference between these two threads?
"ExecuteThread [ASSET]: '10' for queue:"(self-adjusting) weblogic.kernel.Default""-wire t@119
java.lang.Thread.State: pending
at java.lang.Object.wait (Native Method)
-waiting on < 5b3f46a5 > (a weblogic.work.ExecuteThread)
at java.lang.Object.wait(Object.java:485)
at weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Locked ownable Synchronizers:
-None

"[Pending] ExecuteThread: '9' for the queue:"(self-adjusting) weblogic.kernel.Default""-wire t@117
java.lang.Thread.State: pending
at java.lang.Object.wait (Native Method)
-waiting on < 463515a 4 > (a weblogic.work.ExecuteThread)
at java.lang.Object.wait(Object.java:485)
at weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Locked ownable Synchronizers:
-None

Thanks for your help
Hello

[ACTIVE] [EVE] are States that Weblogic assigns to its internal nets.

Most of the time, you will see discussions (waitForRequest) pending pending because they do nothing.

Discussions in the way ASSETS Weblogic kernel assigned a request and that request is in progress.

I saw in some Threads in Thread dump in ACTIVE State, even if they expect a request so not 100% compatible. I worry too much on this subject.

The part of the key to analysis is to analyze the Stack Trace of the Thread and the native state of Thread (RUNNABLE, WAITING), those are your real indicators if the Thread is waiting for a query or really stuck a request for treatment.

-The first line will also give you the current Thread action (waiting to be warned, blocked / stuck on a monitor, computer science etc..)
-The Stack Trace will also give you specify if the Thread is waiting to process a query (free Thread) or a real application or the task of Weblogic internal treatment

Kind regards
PERSON-H

Blocked threads executing confidence Recon

We have a REST base custom connector and run reconciliation trust with it. We get the stuck thread question. Only 500 users are have closer per hour. No idea how to diagnose this problem? A Profiler can help in this case?

Use jvisualvm jdk/bin and connect to oim_server, and the list of all the discussions.

Click on "Thread Dump" to get the State of all discussions and find problematic place.

Export of wire dumps for flight from Java

I couldn't find a way to export the thread dumps taken by JFR by JFR plugin java is mission control. I would like to export in the form of text and analyzed around analysers as TDA (https://java.net/projects/tda). Since there are more than 100 taken thread dumps, copy each of them doesn't seem practical. Do you see an alternative?
Thank you!

Yes. JMC 6.0.0 & JDK 9.

Java dump
Hello

Not sure if this should be in the Unix forum or here, but I am trying to perform a dump thread running on OEL jrockit jvm.

We use 'kill-3 pid' to take a picture, but it doesn't create any file...

Please suggest

Thank you!
If I remember correctly the thread dump is sent to the server log file (when JRockit works for example WebLogic).

You can also do is use jrcmd with the print_threads command, for example, jrcmd PID print_threads > directory/dump.txt

DB Dump slows to Crawl - 100% of CPU usage
We have a BDB occupying about 40 GB of disk, with 3 tables, 2 have about 25 MM records and the 3rd with 1.5 MM records. We have a web service application that works 24/7, with a 'writing' for BDB environment. In a separate JVM using a 'read only' environment for the BDB, I try to empty all the contents of the table (one at a time) of flat files.

I tried the DbDump utility in the pilot of sleepycat, as well as my own program (who has worked in the past on this same DB). The small empty table without problem. Landfills for large tables going at normal speed, but after some time they bog completely to the point of dumping 0-100 records per second... Ouch. When the discharge reaches that level of performance that is painful, it is completely connecting the CPU at 100%. Two large tables, one with the small records exports about 20 MM records before it slows down to a crawl. The one with the big records dumps about 2.5 MM.

If I stop the discharge and start a new cursor to the last ID I threw in the previous race, the new dump starts again at normal speed. So it doesn't seem to be any kind of problem with BDB itself storage. Perhaps there is a leak of some kind in the pilot of sleepycat, or more likely a config that I am misunderstanding.

When you run the last dump of attempt, I printed the environment stats every 5 minutes. Files to the end of the performance show very little difference in the 5 minutes of execution, with the exception of nNodesScanned and nThreadUnavailable set increases. I have really no idea what mean these stats, so I posted a few cuts below for review.

Someone at - it indexes?

Stats 05:25 minutes
==================================
I/o: The log file opens, fsyncs writings, readings, absences from the cache.
bufferBytes = 3, 145, 728
endOfLog = 0xa701/0x1c7005c
nBytesReadFromWriteQueue = 0
nBytesWrittenFromWriteQueue = 0
nCacheMiss = 6, 110, 502
nFSyncRequests = 0
nFSyncTimeouts = 0
nFSyncs = 0
nFileOpens = 62, 910
nLogBuffers = 3
nLogFSyncs = 0
nNotResident = 6, 110, 502
nOpenFiles = 100
nRandomReadBytes = 4, 387, 025 920
nRandomReads = 2, 124, 724
nRandomWriteBytes = 0
nRandomWrites = 0
nReadsFromWriteQueue = 0
nRepeatFaultReads = 230, 139
nSequentialReadBytes = 9, 552, 327, 893
nSequentialReads = 4, 346, 396
nSequentialWriteBytes = 0
nSequentialWrites = 0
nTempBufferWrites = 0
nWriteQueueOverflow = 0
nWriteQueueOverflowFailures = 0
nWritesFromWriteQueue = 0
Cache: Size, assignments and deportation activity.
adminBytes = 94, 858
avgBatchCACHEMODE = 0
avgBatchCRITICAL = 21
avgBatchDAEMON = 0
avgBatchEVICTORTHREAD = 27
avgBatchMANUAL = 0
cacheTotalBytes = 618, 172, 306
614, 931, 584 = dataBytes
lockBytes = 136
nBINsEvictedCACHEMODE = 0
nBINsEvictedCRITICAL = 16, 847
nBINsEvictedDAEMON = 0
nBINsEvictedEVICTORTHREAD = 52, 321
nBINsEvictedMANUAL = 0
nBINsFetch = 6, 537, 087
nBINsFetchMiss = 161, 139
nBINsStripped = 63, 700
nBatchesCACHEMODE = 0
nBatchesCRITICAL = 265
nBatchesDAEMON = 0
nBatchesEVICTORTHREAD = 852
nBatchesMANUAL = 0
nCachedBINs = 91, 827
nCachedUpperINs = 9, 879
nEvictPasses = 4, 250
nINCompactKey = 4, 673
nINNoTarget = 73, 870
nINSparseTarget = 4, 867
nLNsFetch = 18, 230, 686
nLNsFetchMiss = 5, 852, 734
nNodesEvicted = 69, 411
nNodesScanned = 10, 516, 074
nNodesSelected = 135, 241
nRootNodesEvicted = 0
nThreadUnavailable = 6, 359
nUpperINsEvictedCACHEMODE = 0
nUpperINsEvictedCRITICAL = 45
nUpperINsEvictedDAEMON = 0
nUpperINsEvictedEVICTORTHREAD = 201
nUpperINsEvictedMANUAL = 0
nUpperINsFetch = 12, 244, 811
nUpperINsFetchMiss = 10, 199
requiredEvictBytes = 0
sharedCacheTotalBytes = 0
Cleaning: Frequency and extent of the cleansing activity log file.
cleanerBackLog = 0
fileDeletionBacklog = 0
nCleanerDeletions = 0
nCleanerEntriesRead = 0
nCleanerRuns = 0
nClusterLNsProcessed = 0
nINsCleaned = 0
nINsDead = 0
nINsMigrated = 0
nINsObsolete = 0
nLNQueueHits = 0
nLNsCleaned = 0
nLNsDead = 0
nLNsLocked = 0
nLNsMarked = 0
nLNsMigrated = 0
nLNsObsolete = 0
nMarkLNsProcessed = 0
nPendingLNsLocked = 0
nPendingLNsProcessed = 0
nRepeatIteratorReads = 0
nToBeCleanedLNsProcessed = 0
totalLogSize = 46, 529, 378-030
Compression by node: abduction and internal btree nodes.
cursorsBins = 0
dbClosedBins = 0
inCompQueueSize = 0
nonEmptyBins = 0
processedBins = 0
splitBins = 0
Control points: frequency and scope of activity of the control points.
lastCheckpointEnd = 0xa701/0xc5e490
lastCheckpointId = 83, 145
lastCheckpointStart = 0 x 0/0 x 0
nCheckpoints = 0
nDeltaINFlush = 0
nFullBINFlush = 0
nFullINFlush = 0
Environment: Environment general broad statistics.
btreeRelatchesRequired = 363
Locks: Locks held by data operations, lock contention on the lock table.
nLatchAcquireNoWaitUnsuccessful = 0
nLatchAcquiresNoWaitSuccessful = 0
nLatchAcquiresNoWaiters = 0
nLatchAcquiresSelfOwned = 0
nLatchAcquiresWithContention = 0
nLatchReleases = 0
nOwners = 2
nReadLocks = 2
nRequests = 18, 229, 682
nTotalLocks = 2
nWaiters = 0
nWaits = 0
nWriteLocks = 0

Stats 6: 5 minutes after Stats 5 - Normal operation
==========================================================
I/o: The log file opens, fsyncs writings, readings, absences from the cache.
bufferBytes = 3, 145, 728
endOfLog = 0xa701/0x1c7005c
nBytesReadFromWriteQueue = 0
nBytesWrittenFromWriteQueue = 0
nCacheMiss = 7, 059, 709
nFSyncRequests = 0
nFSyncTimeouts = 0
nFSyncs = 0
nFileOpens = 72, 546
nLogBuffers = 3
nLogFSyncs = 0
nNotResident = 7, 059, 709
nOpenFiles = 100
nRandomReadBytes = 5, 043, 661, 824
nRandomReads = 2, 445, 347
nRandomWriteBytes = 0
nRandomWrites = 0
nReadsFromWriteQueue = 0
nRepeatFaultReads = 241, 954
nSequentialReadBytes = 10, 116, 899, 671
nSequentialReads = 4, 996, 431
nSequentialWriteBytes = 0
nSequentialWrites = 0
nTempBufferWrites = 0
nWriteQueueOverflow = 0
nWriteQueueOverflowFailures = 0
nWritesFromWriteQueue = 0
Cache: Size, assignments and deportation activity.
adminBytes = 94, 858
avgBatchCACHEMODE = 0
avgBatchCRITICAL = 17
avgBatchDAEMON = 0
avgBatchEVICTORTHREAD = 27
avgBatchMANUAL = 0
cacheTotalBytes = 618, 139, 394
614, 898, 672 = dataBytes
lockBytes = 136
nBINsEvictedCACHEMODE = 0
nBINsEvictedCRITICAL = 19: 062
nBINsEvictedDAEMON = 0
nBINsEvictedEVICTORTHREAD = 62, 580
nBINsEvictedMANUAL = 0
nBINsFetch = 7, 538, 745
nBINsFetchMiss = 172, 923
nBINsStripped = 76, 024
nBatchesCACHEMODE = 0
nBatchesCRITICAL = 224
nBatchesDAEMON = 0
nBatchesEVICTORTHREAD = 767
nBatchesMANUAL = 0
nCachedBINs = 91, 137
nCachedUpperINs = 9, 885
nEvictPasses = 5, 035
nINCompactKey = 4, 673
nINNoTarget = 72, 507
nINSparseTarget = 4, 781
nLNsFetch = 21, 093, 476
nLNsFetchMiss = 6, 790, 126
nNodesEvicted = 81, 910
nNodesScanned = 12, 784, 174
nNodesSelected = 160, 543
nRootNodesEvicted = 0
nThreadUnavailable = 7, 430
nUpperINsEvictedCACHEMODE = 0
nUpperINsEvictedCRITICAL = 54
nUpperINsEvictedDAEMON = 0
nUpperINsEvictedEVICTORTHREAD = 217
nUpperINsEvictedMANUAL = 0
nUpperINsFetch = 14, 172, 141
nUpperINsFetchMiss = 10, 230
requiredEvictBytes = 0
sharedCacheTotalBytes = 0
Cleaning: Frequency and extent of the cleansing activity log file.
cleanerBackLog = 0
fileDeletionBacklog = 0
nCleanerDeletions = 0
nCleanerEntriesRead = 0
nCleanerRuns = 0
nClusterLNsProcessed = 0
nINsCleaned = 0
nINsDead = 0
nINsMigrated = 0
nINsObsolete = 0
nLNQueueHits = 0
nLNsCleaned = 0
nLNsDead = 0
nLNsLocked = 0
nLNsMarked = 0
nLNsMigrated = 0
nLNsObsolete = 0
nMarkLNsProcessed = 0
nPendingLNsLocked = 0
nPendingLNsProcessed = 0
nRepeatIteratorReads = 0
nToBeCleanedLNsProcessed = 0
totalLogSize = 46, 529, 378-030
Compression by node: abduction and internal btree nodes.
cursorsBins = 0
dbClosedBins = 0
inCompQueueSize = 0
nonEmptyBins = 0
processedBins = 0
splitBins = 0
Control points: frequency and scope of activity of the control points.
lastCheckpointEnd = 0xa701/0xc5e490
lastCheckpointId = 83, 145
lastCheckpointStart = 0 x 0/0 x 0
nCheckpoints = 0
nDeltaINFlush = 0
nFullBINFlush = 0
nFullINFlush = 0
Environment: Environment general broad statistics.
btreeRelatchesRequired = 363
Locks: Locks held by data operations, lock contention on the lock table.
nLatchAcquireNoWaitUnsuccessful = 0
nLatchAcquiresNoWaitSuccessful = 0
nLatchAcquiresNoWaiters = 0
nLatchAcquiresSelfOwned = 0
nLatchAcquiresWithContention = 0
nLatchReleases = 0
nOwners = 2
nReadLocks = 2
nRequests = 21, 092, 472
nTotalLocks = 2
nWaiters = 0
nWaits = 0
nWriteLocks = 0

Stats 35: nearly 3 hours in
==================================
I/o: The log file opens, fsyncs writings, readings, absences from the cache.
bufferBytes = 3, 145, 728
endOfLog = 0xa701/0x1c7005c
nBytesReadFromWriteQueue = 0
nBytesWrittenFromWriteQueue = 0
nCacheMiss = 23, 599, 023
nFSyncRequests = 0
nFSyncTimeouts = 0
nFSyncs = 0
nFileOpens = 245, 062
nLogBuffers = 3
nLogFSyncs = 0
nNotResident = 23, 599, 023
nOpenFiles = 100
nRandomReadBytes = 16, 519, 197, 696
nRandomReads = 8, 048, 636
nRandomWriteBytes = 0
nRandomWrites = 0
nReadsFromWriteQueue = 0
nRepeatFaultReads = 448, 164
nSequentialReadBytes = 34, 342, 084, 162
nSequentialReads = 16, 311, 182
nSequentialWriteBytes = 0
nSequentialWrites = 0
nTempBufferWrites = 0
nWriteQueueOverflow = 0
nWriteQueueOverflowFailures = 0
nWritesFromWriteQueue = 0
Cache: Size, assignments and deportation activity.
adminBytes = 94, 858
avgBatchCACHEMODE = 0
avgBatchCRITICAL = 4
avgBatchDAEMON = 0
avgBatchEVICTORTHREAD = 4
avgBatchMANUAL = 0
cacheTotalBytes = 618, 608, 050
615, 367, 328 = dataBytes
lockBytes = 136
nBINsEvictedCACHEMODE = 0
nBINsEvictedCRITICAL = 47, 462
nBINsEvictedDAEMON = 0
nBINsEvictedEVICTORTHREAD = 250, 549
nBINsEvictedMANUAL = 0
nBINsFetch = 25, 437, 033
nBINsFetchMiss = 378, 634
nBINsStripped = 291, 420
nBatchesCACHEMODE = 0
nBatchesCRITICAL = 202
nBatchesDAEMON = 0
nBatchesEVICTORTHREAD = 2, 377
nBatchesMANUAL = 0
nCachedBINs = 80, 479
nCachedUpperINs = 9, 844
nEvictPasses = 51, 670
nINCompactKey = 4, 673
nINNoTarget = 50, 893
nINSparseTarget = 3, 131
nLNsFetch = 71, 421, 061
nLNsFetchMiss = 23, 123, 231
nNodesEvicted = 298, 815
nNodesScanned = 3, 112, 404, 708
nNodesSelected = 824, 668
nRootNodesEvicted = 0
nThreadUnavailable = 294, 966
nUpperINsEvictedCACHEMODE = 0
nUpperINsEvictedCRITICAL = 125
nUpperINsEvictedDAEMON = 0
nUpperINsEvictedEVICTORTHREAD = 685
nUpperINsEvictedMANUAL = 0
nUpperINsFetch = 48, 198, 643
nUpperINsFetchMiss = 10, 728
requiredEvictBytes = 639
sharedCacheTotalBytes = 0
Cleaning: Frequency and extent of the cleansing activity log file.
cleanerBackLog = 0
fileDeletionBacklog = 0
nCleanerDeletions = 0
nCleanerEntriesRead = 0
nCleanerRuns = 0
nClusterLNsProcessed = 0
nINsCleaned = 0
nINsDead = 0
nINsMigrated = 0
nINsObsolete = 0
nLNQueueHits = 0
nLNsCleaned = 0
nLNsDead = 0
nLNsLocked = 0
nLNsMarked = 0
nLNsMigrated = 0
nLNsObsolete = 0
nMarkLNsProcessed = 0
nPendingLNsLocked = 0
nPendingLNsProcessed = 0
nRepeatIteratorReads = 0
nToBeCleanedLNsProcessed = 0
totalLogSize = 46, 529, 378-030
Compression by node: abduction and internal btree nodes.
cursorsBins = 0
dbClosedBins = 0
inCompQueueSize = 0
nonEmptyBins = 0
processedBins = 0
splitBins = 0
Control points: frequency and scope of activity of the control points.
lastCheckpointEnd = 0xa701/0xc5e490
lastCheckpointId = 83, 145
lastCheckpointStart = 0 x 0/0 x 0
nCheckpoints = 0
nDeltaINFlush = 0
nFullBINFlush = 0
nFullINFlush = 0
Environment: Environment general broad statistics.
btreeRelatchesRequired = 363
Locks: Locks held by data operations, lock contention on the lock table.
nLatchAcquireNoWaitUnsuccessful = 0
nLatchAcquiresNoWaitSuccessful = 0
nLatchAcquiresNoWaiters = 0
nLatchAcquiresSelfOwned = 0
nLatchAcquiresWithContention = 0
nLatchReleases = 0
nOwners = 2
nReadLocks = 2
nRequests = 71, 420, 057
nTotalLocks = 2
nWaiters = 0
nWaits = 0
nWriteLocks = 0

His stats 36: 5 minutes after Stats 35 - abysmal performance
==========================================================
I/o: The log file opens, fsyncs writings, readings, absences from the cache.
bufferBytes = 3, 145, 728
endOfLog = 0xa701/0x1c7005c
nBytesReadFromWriteQueue = 0
nBytesWrittenFromWriteQueue = 0
nCacheMiss = 23, 599, 314
nFSyncRequests = 0
nFSyncTimeouts = 0
nFSyncs = 0
nFileOpens = 245, 063
nLogBuffers = 3
nLogFSyncs = 0
nNotResident = 23, 599, 314
nOpenFiles = 100
nRandomReadBytes = 16, 519, 396, 352
nRandomReads = 8, 048, 733
nRandomWriteBytes = 0
nRandomWrites = 0
nReadsFromWriteQueue = 0
nRepeatFaultReads = 448, 166
nSequentialReadBytes = 34, 342, 490 293
nSequentialReads = 16, 311, 379
nSequentialWriteBytes = 0
nSequentialWrites = 0
nTempBufferWrites = 0
nWriteQueueOverflow = 0
nWriteQueueOverflowFailures = 0
nWritesFromWriteQueue = 0
Cache: Size, assignments and deportation activity.
adminBytes = 94, 858
avgBatchCACHEMODE = 0
avgBatchCRITICAL = 4
avgBatchDAEMON = 0
avgBatchEVICTORTHREAD = 4
avgBatchMANUAL = 0
cacheTotalBytes = 618, 607, 586
615, 366, 864 = dataBytes
lockBytes = 136
nBINsEvictedCACHEMODE = 0
nBINsEvictedCRITICAL = 47, 463
nBINsEvictedDAEMON = 0
nBINsEvictedEVICTORTHREAD = 250, 551
nBINsEvictedMANUAL = 0
nBINsFetch = 25, 462, 823
nBINsFetchMiss = 378, 636
nBINsStripped = 291, 423
nBatchesCACHEMODE = 0
nBatchesCRITICAL = 194
nBatchesDAEMON = 0
nBatchesEVICTORTHREAD = 2, 628
nBatchesMANUAL = 0
nCachedBINs = 80, 478
nCachedUpperINs = 9, 844
nEvictPasses = 54, 594
nINCompactKey = 4, 673
nINNoTarget = 50, 891
nINSparseTarget = 3, 131
nLNsFetch = 71, 447, 426
nLNsFetchMiss = 23, 123, 520
nNodesEvicted = 298, 818
nNodesScanned = 3, 701, 931-012
nNodesSelected = 837, 417
nRootNodesEvicted = 0
nThreadUnavailable = 317, 852
nUpperINsEvictedCACHEMODE = 0
nUpperINsEvictedCRITICAL = 125
nUpperINsEvictedDAEMON = 0
nUpperINsEvictedEVICTORTHREAD = 685
nUpperINsEvictedMANUAL = 0
nUpperINsFetch = 48, 224, 717
nUpperINsFetchMiss = 10, 728
requiredEvictBytes = 175
sharedCacheTotalBytes = 0
Cleaning: Frequency and extent of the cleansing activity log file.
cleanerBackLog = 0
fileDeletionBacklog = 0
nCleanerDeletions = 0
nCleanerEntriesRead = 0
nCleanerRuns = 0
nClusterLNsProcessed = 0
nINsCleaned = 0
nINsDead = 0
nINsMigrated = 0
nINsObsolete = 0
nLNQueueHits = 0
nLNsCleaned = 0
nLNsDead = 0
nLNsLocked = 0
nLNsMarked = 0
nLNsMigrated = 0
nLNsObsolete = 0
nMarkLNsProcessed = 0
nPendingLNsLocked = 0
nPendingLNsProcessed = 0
nRepeatIteratorReads = 0
nToBeCleanedLNsProcessed = 0
totalLogSize = 46, 529, 378-030
Compression by node: abduction and internal btree nodes.
cursorsBins = 0
dbClosedBins = 0
inCompQueueSize = 0
nonEmptyBins = 0
processedBins = 0
splitBins = 0
Control points: frequency and scope of activity of the control points.
lastCheckpointEnd = 0xa701/0xc5e490
lastCheckpointId = 83, 145
lastCheckpointStart = 0 x 0/0 x 0
nCheckpoints = 0
nDeltaINFlush = 0
nFullBINFlush = 0
nFullINFlush = 0
Environment: Environment general broad statistics.
btreeRelatchesRequired = 363
Locks: Locks held by data operations, lock contention on the lock table.
nLatchAcquireNoWaitUnsuccessful = 0
nLatchAcquiresNoWaitSuccessful = 0
nLatchAcquiresNoWaiters = 0
nLatchAcquiresSelfOwned = 0
nLatchAcquiresWithContention = 0
nLatchReleases = 0
nOwners = 2
nReadLocks = 2
nRequests = 71, 446, 422
nTotalLocks = 2
nWaiters = 0
nWaits = 0
nWriteLocks = 0
Please report the thread dumps. These show what we expect, if our hypothesis on the cause of the problem is correct.
-mark

Is there a way to see the files opened by java threads
-environment-
Java for 64-bit Server VM (build 1.5.0_19 - b02, mixed mode)
Linux 2.6.9 - 78.0.5.ELsmp #1 SMP Wed Sep 24 12:40:24 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
Xeon of Intel (r) CPU
--------------------------

Hi all

I would like to know if, in the course of an outOfMemory, there are ways to:
1. do you have a list of thread for the time (basically a thread dump)
2. know the thread which lead to the OOM (even if the thread could well be the 'drop' leading to OOM)
3. get a summary of the brief files on track to open by thread (basically a dump of the heap) use java.
4. get a list of files opened by my thread

Our application is regularly faced with outOfMemory (OOM) and I know that this sometimes load important file, so now I'm testing is the use of hprof (-agentlib:hprof = heap = sites, thread = y, depth = 2). Send "kill-3" on my java process creates a file containing a thread dump + memory usage. But it can't help me for question 2.

Regarding question 4, I tried to establish a correlation between the hprof output + pstack + jstack, pmap, but I'm not the info I'm looking for (pstack, jstack do not show the address of open files)

Finally, if this isn't the right forum for my question, please tell me where to post it.

Thank you
Have you tried - XX: + HeapDumpOnOutOfMemoryError?

I would use a recent version of Java as Java 6 update 25.

You can get a list of files opened by looking at/proc / {pid} /fd/ however you should never be allowed to open as many files as you run out of memory.

If you use a Profiler, you can see that the son made at some point, and where objects are allocated.

I don't think you can associate files with a wire.

125, hogging threads waiting for lock oracle.jdbc.driver.T4CConnection@5500
We use DBAdapter in soa suite 11 g (xa thin drivers, AIX platform) to talk to the database. At one point today, we could see the system WLS slows down considerably and thread dumps could see 125 hogging son everyone waits for the next lock:

' ExecuteThread: '16' for queue: '(self-adjusting) weblogic.kernel.Default' "waiting for lock *oracle.jdbc.driver.T4CConnection@55005500* BLOCKED
oracle.jdbc.driver.T4CXAResource.doRollback(T4CXAResource.java:648)
oracle.jdbc.xa.client.OracleXAResource.rollback(OracleXAResource.java:1148)
weblogic.jdbc.wrapper.VendorXAResource.rollback(VendorXAResource.java:78)
weblogic.jdbc.jta.DataSource.rollback(DataSource.java:1146)

Can someone point to this oracle.jdbc.driver.T4CConnection@55005500. Is that a lock on a connection object? If so this means that all 125 discussions were waiting for a single connection? The source of data used has default settings for the connection pool.

I couldn't see any thread thread discharge which States that it is now the same lock, possibly could be a problem with the way thread dump is generated in AIX

Can someone shed some light on this?
Hello. Grep just for T4CConnection@55005500 in the discharge. You will see the number of threads
blocked (as you would expect) on this point, but only one thread that already have this object
locked and uses it. Unfortunately, the thread is suspended in a call to DBMS, so it cannot
go ahead and release the connection object and let all other threads proceed.
I has you pointed out only one thread.

Stuck threads / slow response.
We have a problem with our application running on weblogic 9.2. Some applications are working fine, others remain blocked. Studied for some time, but no clear indication of what the problem is yet.

Last thread dumps have a large number of occurences of the following type
```
"[ACTIVE] ExecuteThread: '48' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.servlet.jsp.JavelinxJSPStub@c469fb BLOCKED
     weblogic.servlet.jsp.JspStub.checkForReload(JspStub.java:119)
     weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:232)
     weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
        . . . 

"[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock javelin.client.JobWaiter@ef27d1 WAITING
     java.lang.Object.wait(Native Method)
     java.lang.Object.wait(Object.java:474)
     javelin.client.JobWaiter.blockUntilFinished(JobWaiter.java:45)
      javelin.client.ClientUtilsImpl.build(ClientUtilsImpl.java:859)
     weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:250)
        . . . 
```
Suggests that we have a problem with jsp compilations?

Or is it likely just a symptom of a different problem?
Hello

It seems that WebLogic trying to check for the resource JSP reload... and he's STUCK in this process...

By chance you tried to disable the 'resource-charging-check-dry' in weblogic.xml by assigning the value "-1".
(http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webapp/weblogic_xml.html)
And "* page-check-seconds *" in weblogic.xml "-1".»

resources-charging-check-dry
The element is used to perform caching for cached resources that are found in the path of resource in the scope of the metadata Web. This parameter identifies the frequency of WebLogic Server checks to see if a resource has been changed and if so, it recharges.
A value of-1 means never charge. This is the default value in a production environment.
The value 0 means always reload.
A value of 1 means that reload every second. This is the default value in a development environment.
The values specified for this parameter using the administration Console prevail.

page-check-seconds Sets the interval, in seconds, that WebLogic Server checks if the JSP files have changed and need to recompile. The dependencies are also checked and recursively reloaded if changed.
A value of-1 means never check the man pages. This is the default value in a production environment.
The value 0 means always check the man pages.
The value 1 means check the pages every second. This is the default value in a development environment.
In a production environment where changes to a JSP page are scarce, consider changing the value of pageCheckSeconds to 60 or more, according to your needs setting.

Deactivation of the "page-check-seconds' can help to understand this issue...

Thank you
Jay SenSharma

SimpleParser consistency class is not thread-safe?
Coherense has the utility class to XML very convinent which we use it a lot in our coherence-related applications.

But meet us some lock mysterious question (dead end, maybe?) and have identified that it would be that the com.tangosol.run.xml.SimpleParser class is not thread-safe.

We use tomcat 6 and Spring 2.0.6.

Application Web has 2 bean that implements the InitializingBean interface.

Bean A afterPropertiesSet() method will use com.tangosol.run.xml.XmlHelper.loadXml method to parse a XML file.
Method of Bean B afterPropertiesSet() will acts as a tcp expand clients and retrieve data from a cluster of coherence. Which, I think, consistency will also use XML class useful during parsing of the configuration files.

We meet randomly blocking of tomcat (which never end starting webapp deployment alternation) as 1 on 2 or 3 tests.

Use of jconsole and tomcat connection we can see that the main thread stuck in the class SimpleParser. Here's the thread dump.

Name: main
State: EXECUTABLE
Blocked in total: 156 Total expected: 0

*************************************************************************************************

Stack trace:
com.tangosol.run.xml.SimpleParser.instantiateDocument(SimpleParser.java:150)
com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:115)
-locking com.tangosol.run.xml.SimpleParser@f10c77
com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:71)
com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:84)
com.tangosol.run.xml.XmlHelper.loadXml(XmlHelper.java:109)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425)
org.springframework.beans.factory.support.AbstractBeanFactory$ 1.getObject(AbstractBeanFactory.java:251)
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
-locking java.util.concurrent.ConcurrentHashMap@dee55c
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:287)
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
-locking java.lang.Object@d21555
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:244)
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:187)
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3830)
org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
-locking org.apache.catalina.core.StandardContext@1c64ed8
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
-locking java.util.HashMap@76a6d9
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
-locking org.apache.catalina.core.StandardHost@1c42c4b
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
-locking org.apache.catalina.core.StandardHost@1c42c4b
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
-locking org.apache.catalina.core.StandardEngine@37fd24
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
org.apache.catalina.core.StandardService.start(StandardService.java:516)
-locking org.apache.catalina.core.StandardEngine@37fd24
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
-locked [Lorg.apache.catalina.Service;@1cc55fb
org.apache.catalina.startup.Catalina.start(Catalina.java:566)
sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke (unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)
java.lang.reflect.Method.invoke (unknown Source)
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
org.apache.catalina.startup.Bootstrap.main (Bootstrap.java:413)

*************************************************************************************************

After we have add the tag is based on applying bean B wait on A bean to complete initialization, we encounter is no longer blocked when starting tomcat.

We suspect that maybe SimpleParser class is not thread-safe and will cause potential deadlock issue.

Published by: user639604 on June 22, 2009 10:36
It seems that the 'hand' thread comes to the point that he is responsible for the class of SimpleDocument around the same time as the thread "Timer-0"comes to the point where he is in charge of the class ExternalizableHelper. According to what son get on-demand, if the loading of the class ExternalizableHelper happens point of needing to SimpleDocument after the main thread starts to load SimpleDocument, then a deadlock (inside the JVM loading infrastructure class) happen.

While you are correct that it is our fault (we shouldn't have used a subset of the ExternalizableHelper static initializer), there is probably a simple solution; Just do the following in an initializer static for your first loads or the classes related to the coherence, for example ClusterConfigurator and OPCacheManager:
```
static
  {
  // this should force the ExternalizableHelper class to be loaded
  ExternalizableHelper.makeTrint(0L);
  }
```
Peace,

Cameron Purdy | The Oracle coherence

Stuck Thread definition & what of Weblogic with her
Hello

I have the following situation:
Long-running transaction (approximately 1200 s). Transaction timeout - 3600 s Stuck thread max time - 600 sec. After 1500 dry a Stuck Thread exception comes and treatment of "blockages" until you restart.
After changing the time max wire stuck to 3600 sec the success of treatment.

This topic, I have a few questions on the State of Stuck in Weblogic 10:
(1) when a thread will be marked as Stuck? Only when it "hangs" or it takes too long too? Is not a necessary condition for transaction-timeout > stuck-thread-max-time
(2) what more weblogic with this Thread Stuck? Upstream of the reduction of the CPU? Fact frozen?

Thanks in advance.
To my knowledge, when a thread is time consuming (time max more than configured blocked thread) for a transaction, then this thread is marked as stuck.
But this does not mean that the particular thread is stuck forever.
Change time Stuck Thread Max does not affect the behavior of threads in some way.

The stuck thread can run in full after a few time and weblogic makes the not blocked thread.
Usually the back-end calls, sometimes take a long time.
To find out exactly what is happening during this time, take a thread dump and the search for the Thread stack running, which has been shown as stuck in the newspapers.

The fact that thread takes a lot of time until the end is generally bad.
Users do not make the patient.

Published by: gvamsius on March 10, 2009 08:33

thread dumps

Similar Questions

Maybe you are looking for