[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2209
  • Last Modified:

Weblogic 10 g : Thread Dump Analysis too many Standby threads

I find too many Stand by threads in the Thread Analysis . Please explain the possible reason.

[STANDBY] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'" id=38370 idx=0xe4 tid=21759 prio=5 alive, in native, waiting, daemon
         
                -- Waiting for notification on: weblogic/work/ExecuteThread@0x4a1480f0[fat lock]
         
                at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
         
                at jrockit/vm/Locks.wait(Locks.java:2261)[inlined]
         
                at java/lang/Object.wait(Object.java:485)[inlined]
         
                at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)[inlined]
         
                at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)[optimized]
         
                ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x4a1480f0[fat lock]
         
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
         
                -- end of trace
          [STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" id=59 idx=0x100 tid=4719 prio=5 alive, in native, waiting, daemon
         
                -- Waiting for notification on: weblogic/work/ExecuteThread@0x4321d5b8[fat lock]
         
                at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
         
                at jrockit/vm/Locks.wait(Locks.java:2261)[inlined]
         
                at java/lang/Object.wait(Object.java:485)[inlined]
         
                at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)[optimized]
         
                ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x4321d5b8[fat lock]
         
                at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
         
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
         
                -- end of trace
         
            "Thread-17" id=60 idx=0x104 tid=4720 prio=5 alive, in native, sleeping, native_waiting, daemon
         
                at java/lang/Thread.sleep(J)V(Native Method)
         
                at org/apache/log4j/helpers/FileWatchdog.run(FileWatchdog.java:103)
         
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
         
                -- end of trace
         
            "weblogic.cluster.MessageReceiver" id=61 idx=0x108 tid=4721 prio=5 alive, in native, daemon
         
                at java/net/PlainDatagramSocketImpl.receive0(Ljava/net/DatagramPacket;)V(Native Method)
         
                ^-- Holding lock: java/net/PlainDatagramSocketImpl@0x432ea3a8[recursive]
         
                at java/net/PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
         
                ^-- Holding lock: java/net/PlainDatagramSocketImpl@0x432ea3a8[biased lock]
         
                at java/net/DatagramSocket.receive(DatagramSocket.java:712)
         
                ^-- Holding lock: java/net/DatagramPacket@0x540506e8[biased lock]
         
                ^-- Holding lock: java/net/MulticastSocket@0x432ea3f8[biased lock]
         
                at weblogic/cluster/MulticastFragmentSocket.receive(MulticastFragmentSocket.java:211)
         
                at weblogic/cluster/FragmentSocketWrapper.receive(FragmentSocketWrapper.java:98)
         
                at weblogic/cluster/MulticastManager.run(MulticastManager.java:457)
         
                at java/lang/Thread.run(Thread.java:619)
         
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
         
                -- end of trace
         
            "[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=62 idx=0x10c tid=4730 prio=5 alive, in native, waiting, daemon
         
                -- Waiting for notification on: weblogic/work/ExecuteThread@0x432f6728[fat lock]
         
                at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
         
                at jrockit/vm/Locks.wait(Locks.java:2261)[inlined]
         
                at java/lang/Object.wait(Object.java:485)[inlined]
         
                at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)[optimized]
         
                ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x432f6728[fat lock]
         
                at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
         
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
         
                -- end of trace
         
            "[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" id=63 idx=0x110 tid=4731 prio=5 alive, in native, waiting, daemon
         
                -- Waiting for notification on: weblogic/work/ExecuteThread@0x432f8100[fat lock]
         
                at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
         
                at jrockit/vm/Locks.wait(Locks.java:2261)[inlined]
         
                at java/lang/Object.wait(Object.java:485)[inlined]
         
                at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:157)[optimized]
         
                ^-- Lock released while waiting: weblogic/work/ExecuteThread@0x432f8100[fat lock]
         
                at weblogic/work/ExecuteThread.run(ExecuteThread.java:178)
         
                at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
         
                -- end of trace
         
0
nxrp
Asked:
nxrp
  • 2
  • 2
1 Solution
 
ECollinCommented:
These threads are just waiting for requests.
0
 
nxrpAuthor Commented:
The dump that I took had 23 stand by threads, would it effect the performance or increase the response time...?
0
 
nxrpAuthor Commented:
The dump that I took had 23 stand by threads, would it effect the performance or increase the response time...?
0
 
ECollinCommented:
not at all. Only running and blocked threads will have an impact on performance.
0
 
sweetfa2Commented:
ECollin's comment is not entirely true,  non-running threads will use memory resources which can affect performance, however in the essence of your question he is correct.  Whether that affects performance will depend on the amount of memory consumed in your JVM.

In some instances the more threads waiting the better the performance will be as new threads do not have the overhead of being created under loaded conditions.

WebLogic will increase threads to accomodate load up to a certain limit.  This is normal and expected behaviour.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now