1 Reply Latest reply: Jan 4, 2013 3:55 PM by anjhawar - oracle RSS

    Weblogic server stopped responding

    VIJAYTechM
      Hi,
      I have problem with weblogic server. It is showing running but it is not responding. So it is showing warning and Not responding Please check the thread dump and suggest me how to avoid this problem for ever.

      Fri Jan 04 11:28:34 2013

      Oracle JRockit(R) R28.1.1-14_BR11718574-141097-1.6.0_22-20110204-1552-windows-x86_64

      "Main Thread" id=1 idx=0x4 tid=4244 prio=5 alive, waiting, native_blocked

      -- Waiting for notification on: weblogic/t3/srvr/T3Srvr@0x000000000505A3F0[fat lock]

      at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)

      at java/lang/Object.wait(J)V(Native Method)

      at java/lang/Object.wait(Object.java:485)

      at weblogic/t3/srvr/T3Srvr.waitForDeath(T3Srvr.java:902)

      ^-- Lock released while waiting: weblogic/t3/srvr/T3Srvr@0x000000000505A3F0[fat lock]

      at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:465)

      at weblogic/Server.main(Server.java:67)

      at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)

      -- end of trace

      "(OC Main Thread)" id=2 idx=0x8 tid=7428 prio=5 alive, native_waiting, daemon

      "(GC Worker Thread 1)" id=? idx=0xc tid=4808 prio=5 alive, daemon

      "(GC Worker Thread 2)" id=? idx=0x10 tid=6996 prio=5 alive, daemon

      "(GC Worker Thread 3)" id=? idx=0x14 tid=5844 prio=5 alive, daemon

      "(GC Worker Thread 4)" id=? idx=0x18 tid=2656 prio=5 alive, daemon

      "(Code Generation Thread 1)" id=3 idx=0x1c tid=5872 prio=5 alive, native_waiting, daemon

      "(Code Optimization Thread 1)" id=4 idx=0x20 tid=7784 prio=5 alive, native_waiting, daemon

      "(VM Periodic Task)" id=5 idx=0x24 tid=7860 prio=10 alive, native_blocked, daemon

      "(Attach Listener)" id=6 idx=0x28 tid=3324 prio=5 alive, native_blocked, daemon

      "Finalizer" id=7 idx=0x2c tid=7596 prio=8 alive, native_waiting, daemon

      at jrockit/memory/Finalizer.waitForFinalizees(J[Ljava/lang/Object;)I(Native Method)
               
                      at jrockit/memory/Finalizer.access$700(Finalizer.java:12)
               
                      at jrockit/memory/Finalizer$4.run(Finalizer.java:189)
               
                      at java/lang/Thread.run(Thread.java:662)
               
                      at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
               
                      -- end of trace
               
                  "Reference Handler" id=8 idx=0x30 tid=7380 prio=10 alive, native_waiting, daemon
               
                      at java/lang/ref/Reference.waitForActivatedQueue(J)Ljava/lang/ref/Reference;(Native Method)
               
                      at java/lang/ref/Reference.access$100(Reference.java:11)
               
                      at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:82)
               
                      at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
               
                      -- end of trace
               
                  "(Sensor Event Thread)" id=9 idx=0x34 tid=5556 prio=5 alive, native_blocked, daemon
               
                  "VM JFR Buffer Thread" id=11 idx=0x38 tid=4496 prio=5 alive, in native, daemon
               
                  "Timer-0" id=13 idx=0x3c tid=4812 prio=5 alive, waiting, native_blocked, daemon
               
                      -- Waiting for notification on: java/util/TaskQueue@0x0000000004B47488[fat lock]

      at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)

      at java/lang/Object.wait(J)V(Native Method)

      at java/lang/Object.wait(Object.java:485)

      at java/util/TimerThread.mainLoop(Timer.java:483)

      ^-- Lock released while waiting: java/util/TaskQueue@0x0000000004B47488[fat lock]

      at java/util/TimerThread.run(Timer.java:462)

      at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)

      -- end of trace

      Thanksm in Adavnce
      Regards,
      Vijay
        • 1. Re: Weblogic server stopped responding
          anjhawar - oracle
          The shared information does not help. Can you please consider collecting a few thread dumps at the time of the issue (if this is replicable) either using WLST or using ctrl+break on the command prompt you are running the WLS node.

          Additionally, is the thread dump collected from the same node that was facing the issue? And how are you confirming that the server process is non responsive?

          AJ