My Oracle Support Banner

Problem Applying a WLS PSU Patch 26519417 - JVM Startup Issue (Doc ID 2359941.1)

Last updated on FEBRUARY 15, 2018

Applies to:

Oracle WebLogic Server - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

Weblogic cluster with two nodes version 12.1.3.0.0
Dynamic cluster
java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
Loadbalancing failover Default Load Algorithm is Round-robin

Applying PSU Patch 26519417 

Followed the steps :

1. Stop all java processes in node 1.

2. Applied patch with Opatch utility.

3. Start nodemanager, AdminServer and managed instances.

But could not do the same in node 2 because when we stop the instance in that node 2, the node 1 instance was in Failed state.

And we get the errors:

"<Jan 17, 2018 2:21:56 PM CET> <Error> <Health> <BEA-310001> <Subsystem DatabaseLessLeasing has failed. Setting server state to FAILED.>
<Jan 17, 2018 2:21:56 PM CET> <Critical> <WebLogicServer> <BEA-000385> <Server health failed. Reason: health of critical service 'DatabaseLessLeasing' failed>
<Jan 17, 2018 2:21:56 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<Jan 17, 2018 2:21:56 PM CET> <Error> <> <BEA-000000> <THREAD DUMP from JVM taken at 'Wed Jan 17 14:21:56 2018'

"

"[STANDBY] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x00007f5d442b4000 nid=0x1864 in Object.wait() [0x00007f5d27c20000]
  java.lang.Thread.State: WAITING (on object monitor)
       at java.lang.Object.wait(Native Method)
       - waiting on <0x00000007da89ba38> (a weblogic.work.ExecuteThread)
       at java.lang.Object.wait(Object.java:503)
       at weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:247)
       - locked <0x00000007da89ba38> (a weblogic.work.ExecuteThread)
       at weblogic.work.ExecuteThread.run(ExecuteThread.java:281)

"DynamicListenThread[Default]" daemon prio=10 tid=0x00007f5d4c079000 nid=0x1863 runnable [0x00007f5d27d21000]
  java.lang.Thread.State: RUNNABLE
       at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
       at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:241)
       - locked <0x00000007dcb88750> (a java.lang.Object)
       at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:31)
       at weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:532)
       at weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:414)
       at weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
       at java.lang.Thread.run(Thread.java:745)

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.