NodeManager Errors after Oracle Flow Builder Patch 31996632 Installation: NMProcess: java.io.IOException: Could not obtain exclusive lock
(Doc ID 2761746.1)
Last updated on MAY 09, 2023
Applies to:
Oracle Application Testing Suite - Version 13.3.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle Application Testing Suite generates fatal error in NodeManager server after application of patch 31996632 for Oracle Flow Builder (OFB).
The "control.sh start" command results in this response:
NMProcess:PM weblogic.nodemanager.server.NMServer main
NMProcess: SEVERE: Fatal error in NodeManager server
NMProcess: java.io.IOException: Could not obtain exclusive lock with lockFile '/u01/oracle/oracleofb/ofb/nodemanager/nodemanager.process.lck'. This most likely indicates another NodeManager process is already running in this NodeManaagerHome.
NMProcess: at weblogic.nodemanager.server.NMServer.getNMFileLock(NMServer.java:254)
NMProcess: at weblogic.nodemanager.server.NMServer.(NMServer.java:153)
NMProcess: at weblogic.nodemanager.server.NMServer.getInstance(NMServer.java:134)
NMProcess: at weblogic.nodemanager.server.NMServer.main(NMServer.java:589)
NMProcess: at weblogic.NodeManager.main(NodeManager.java:31)
NMProcess:
NMProcess: + status=1
NMProcess: + set +x
NMProcess: /u01/oracle/oracleofb/ofb
NMProcess: Stopped draining NMProcess
NMProcess: Stopped draining NMProcess
Successfully Connected to Node Manager.
wls:/nm/ofb> /u01/oracle/oracleofb/scripts
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 |