Knowledge Sharing

arun
August 3rd, 2010 on 11:56 am

Hi Vinoth,

Can you make it clear on development vs production mode with respective Lock feature ?

What do you mean by saying like the “Lock&Edit” feature NOT available in production?

I’m working in production mode , and i can use this feature without any problem.

I click on Lock&Edit from console , apply my changes , and then finally release it! , so that works fine for me.

Let me know if anything wrong in my assumption , and awaiting for your valauble points for me.

Thanks Much

JaySenSharma
August 3rd, 2010 on 1:10 pm
Hi Arun,

From WLS10.3 onwards enabling and disabling feature of Lock & Edit button is added.
Login to AdminConsole—> Click on (Preference) link —-> User preferences (Tab) —->Bottom off the page you will see a check box: Automatically Acquire Lock and Activate Changes

Try to check and Uncheck that Field in production and development Mode…and then check if you see any differences in both scenarios?

.
.
Keep Posting 🙂
Thanks
Jay SenSharma

Log in to Reply

arun
August 3rd, 2010 on 1:19 pm

Thanks Jay

I got the difference in both cases , thanks for clarifying!

–Arun

arun
August 4th, 2010 on 10:49 am

That sounds good to me..

Thanks much Vinoth for your help!

I’ve one question , but not sure whether i can ask here or not..

A very important part of WebLogic Administration is to do with resolving and troubleshooting issues most notably in Production.

Our value is determined by how well we diagnose the problems, bring the services up, determine the root cause of the issue and prevent it from happening in future.

The following are typical reports from users for issues

* The application does not respond and browser just clocks

* Users receiving a page that says Internal Server intermittently

* Users receiving pages that have “404” – Page not found intermittently

* Users getting Page cannot be displayed errors intermittently

* The application is being very slow than usual

What are basic/common approaches to these types of problems…?

–Arun

JaySenSharma
August 4th, 2010 on 12:12 pm
Hi Arun,
There is no hard runles to investigate these kind of issues because every time for these kind of issues we find different root causes…. It can be solved by analyzing the Logs/out/debugging only. How to start debugging these issue …is simply “Look at the server logs…if you dont find much informations then enable debug flags to get more informations….etc”

* The application does not respond and browser just clocks …Take 5-6 Thread Dumps in the interval of 10-12 seconds each… and analyze them.

* Users receiving a page that says Internal Server intermittently Internal Server Error or Error Code 500 in the browser means you need to look into the server Logs to find out the root cause of failure

* Users receiving pages that have “404″ – Page not found intermittently Check the “access.log” request is reaching to server or not for the correct resource…Check the URL is correct or not? Check the Server Logs for any kind of Application related WARNNING or Error Message. You can even check the application logs (if you have any).

* Users getting Page cannot be displayed errors intermittently. Check the “access.log” request is reaching to server or not for the correct resource…Check the URL is correct or not? Check the Server Logs for any kind of Application related WARNNING or Error Message. You can even check the application logs (if you have any).

* The application is being very slow than usual. Take 5-6 Thread Dumps in the interval of 10-12 seconds each… and analyze them.

.
.
Keep Posting 🙂
Thanks
Jay SenSharma

Log in to Reply

arun
August 4th, 2010 on 12:20 pm

Great!

Thanks , let me follow your steps next time when i face these issues again , and still if i had issues I’ll update you.

Thanks again Jay.

arun
August 4th, 2010 on 5:58 pm

Thanks for the information.

I’ll let you know incase of any issues in my app.

Thanks
Arun

suryadhart
August 5th, 2010 on 7:21 pm

Hi,
How can we decide when to use JMS Queues( or JMS Messaging Bridges) and MQ for interacting with other systems.

It would be better if pros & cons are provided.

Cheers,
Surya.

ravikumar
August 18th, 2010 on 1:50 am

Hi Jay
I will first say Thanks to you and faisal for sharing such a good info about weblogic . This site will helping to everyone who intrested in weblogic administration.

I need your help to understand Thread Dump(TD).
As per your post there are many ways we can take thread dumps, But how we can understand it.

for eg I am pasting here some part of TD.
requesting you to please provide your inputs for same.
=======================================================

===== FULL THREAD DUMP ===============

Fri Aug 13 10:24:24 2010

BEA JRockit(R) R27.6.0-50_o_CR373585-101992-1.5.0_15-20080813-1049-linux-ia32

“Main Thread” id=1 idx=0x4 tid=28104 prio=5 alive, in native, waiting

— Waiting for notification on: weblogic/t3/srvr/T3Srvr@0x86b9a98[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:474)

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

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

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

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

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

— end of trace

“(Signal Handler)” id=2 idx=0x8 tid=28105 prio=5 alive, in native, daemon

“(GC Main Thread)” id=3 idx=0xc tid=28106 prio=5 alive, in native, native_waiting, daemon

“(GC Worker Thread 1)” id=? idx=0x10 tid=28107 prio=5 alive, in native, daemon

“(GC Worker Thread 2)” id=? idx=0x14 tid=28108 prio=5 alive, in native, daemon

“(GC Worker Thread 3)” id=? idx=0x18 tid=28109 prio=5 alive, in native, daemon

“(GC Worker Thread 4)” id=? idx=0x1c tid=28110 prio=5 alive, in native, daemon

“(GC Worker Thread 5)” id=? idx=0x20 tid=28111 prio=5 alive, in native, daemon

“(GC Worker Thread 6)” id=? idx=0x24 tid=28112 prio=5 alive, in native, daemon

“(GC Worker Thread 7)” id=? idx=0x28 tid=28113 prio=5 alive, in native, daemon

“(GC Worker Thread 8)” id=? idx=0x2c tid=28114 prio=5 alive, in native, daemon

“(Code Generation Thread 1)” id=4 idx=0x30 tid=28115 prio=5 alive, in native, native_waiting, daemon

“(Code Optimization Thread 1)” id=5 idx=0x34 tid=28116 prio=5 alive, in native, native_waiting, daemon

“(VM Periodic Task)” id=6 idx=0x38 tid=28117 prio=10 alive, in native, daemon

“Finalizer” id=7 idx=0x3c tid=28118 prio=8 alive, in native, native_waiting, daemon

at jrockit/memory/Finalizer.waitForFinalizees([Ljava/lang/Object;)I(Native Method)

at jrockit/memory/Finalizer.access$500(Finalizer.java:12)

at jrockit/memory/Finalizer$4.run(Finalizer.java:159)

at java/lang/Thread.run(Thread.java:595)

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

— end of trace

“Reference Handler” id=8 idx=0x40 tid=28119 prio=10 alive, in native, native_waiting, daemon

at java/lang/ref/Reference.waitForActivatedQueue()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:79)

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

— end of trace

“(Sensor Event Thread)” id=9 idx=0x44 tid=28120 prio=5 alive, in native, daemon

“Timer-0” id=12 idx=0x48 tid=28121 prio=5 alive, in native, waiting, daemon

— Waiting for notification on: java/util/TaskQueue@0x8597528[fat lock]

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

at jrockit/vm/Locks.wait(Locks.java:2250)[inlined]

at java/lang/Object.wait(Object.java:474)[optimized]

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

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

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

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

— end of trace

“Timer-1” id=13 idx=0x4c tid=28165 prio=5 alive, in native, waiting, daemon

— Waiting for notification on: java/util/TaskQueue@0xb084b20[fat lock]

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

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

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

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

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

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

— end of trace

“[STANDBY] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)'” id=14 idx=0x50 tid=28166 prio=5 alive, in native, waiting, daemon

— Waiting for notification on: weblogic/work/ExecuteThread@0xa5d7178[fat lock]

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

at jrockit/vm/Locks.wait(Locks.java:2250)[inlined]

at java/lang/Object.wait(Object.java:474)[inlined]

at weblogic/work/ExecuteThread.waitForRequest(ExecuteThread.java:165)[optimized]

^– Lock released while waiting: weblogic/work/ExecuteThread@0xa5d7178[fat lock]

at weblogic/work/ExecuteThread.run(ExecuteThread.java:186)

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

— end of trace

“weblogic.time.TimeEventGenerator” id=15 idx=0x54 tid=28167 prio=9 alive, in native, waiting, daemon

— Waiting for notification on: weblogic/time/common/internal/TimeTable@0xa9ba5b0[fat lock]

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

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

at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)

^– Lock released while waiting: weblogic/time/common/internal/TimeTable@0xa9ba5b0[fat lock]

at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)

at java/lang/Thread.run(Thread.java:595)

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

— end of trace

“JMAPI event thread” id=16 idx=0x58 tid=28168 prio=5 alive, in native, native_waiting, daemon

“weblogic.timers.TimerThread” id=17 idx=0x5c tid=28169 prio=9 alive, in native, waiting, daemon

— Waiting for notification on: weblogic/timers/internal/TimerThread@0xac0efd0[fat lock]

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

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

at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:260)

^– Lock released while waiting: weblogic/timers/internal/TimerThread@0xac0efd0[fat lock]

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

— end of trace

“[ACTIVE] ExecuteThread: ‘1’ for queue: ‘weblogic.kernel.Default (self-tuning)'” id=18 idx=0x60 tid=28170 prio=5 alive, in native, daemon

at java/net/PlainDatagramSocketImpl.receive0(Ljava/net/DatagramPacket;)V(Native Method)

^– Holding lock: java/net/PlainDatagramSocketImpl@0xa2d3f70[recursive]

at java/net/PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)

^– Holding lock: java/net/PlainDatagramSocketImpl@0xa2d3f70[thin lock]

at java/net/DatagramSocket.receive(DatagramSocket.java:712)

^– Holding lock: java/net/DatagramPacket@0x21788670[thin lock]

^– Holding lock: java/net/MulticastSocket@0xa2d3f38[thin lock]

at weblogic/cluster/FragmentSocket.receive(FragmentSocket.java:202)

at weblogic/cluster/MulticastManager.run(MulticastManager.java:400)

at weblogic/work/ExecuteThread.execute(ExecuteThread.java:209)

at weblogic/work/ExecuteThread.run(ExecuteThread.java:181)

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

— end of trace

“weblogic.store.WLS_DIAGNOSTICS” id=19 idx=0x64 tid=30093 prio=10 alive, in native, parked, daemon

at jrockit/vm/Locks.park0(J)V(Native Method)

at jrockit/vm/Locks.park(Locks.java:2506)

at sun/misc/Unsafe.park(ZJ)V(Native Method)

at java/util/concurrent/locks/LockSupport.park(LockSupport.java:118)

at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)

at java/util/concurrent/LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)

at weblogic/utils/concurrent/JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)

at weblogic/store/internal/PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:570)

at weblogic/store/internal/PersistentStoreImpl.run(PersistentStoreImpl.java:618)

at java/lang/Thread.run(Thread.java:595)

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

— end of trace

“ExecuteThread: ‘0’ for queue: ‘weblogic.socket.Muxer'” id=20 idx=0x68 tid=30096 prio=5 alive, in native, blocked, daemon

— Blocked trying to get lock: weblogic/socket/PosixSocketMuxer$1@0xb0ef598[fat lock]

at jrockit/vm/Threads.waitForUnblockSignal()V(Native Method)

at jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1674)[inlined]

at jrockit/vm/Locks.fatLockReacquire(Locks.java:1912)[optimized]

at jrockit/vm/Locks.lockFat(Locks.java:1780)[optimized]

at jrockit/vm/Locks.monitorEnterSecondStageHard(Locks.java:1311)[optimized]

at jrockit/vm/Locks.monitorEnterSecondStage(Locks.java:1258)[optimized]

at jrockit/vm/Locks.monitorEnter(Locks.java:2455)[optimized]

at weblogic/socket/PosixSocketMuxer.processSockets(PosixSocketMuxer.java:93)

at weblogic/socket/SocketReaderRequest.run(SocketReaderRequest.java:29)

at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:42)

at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:145)

at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:117)

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

— end of trace

“ExecuteThread: ‘1’ for queue: ‘weblogic.socket.Muxer'” id=21 idx=0x6c tid=30097 prio=5 alive, in native, blocked, daemon

— Blocked trying to get lock: weblogic/socket/PosixSocketMuxer$1@0xb0ef598[fat lock]

at jrockit/vm/Threads.waitForUnblockSignal()V(Native Method)

at jrockit/vm/Locks.fatLockBlockOrSpin(Locks.java:1674)[optimized]

at jrockit/vm/Locks.lockFat(Locks.java:1775)[optimized]