Problems starting node manager after WLS 10.3.5 install (I know it’s old – I was augmenting an existing install).
Chose the JDK, used two different JRoickits… Still nodemanager would never start, got the following:
<30/06/2014 3:53:05 PM> <INFO> <Loading domains file: D:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
<30/06/2014 3:53:05 PM> <WARNING> <Domains file not found: D:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
<30/06/2014 3:53:05 PM> <SEVERE> <Fatal error in node manager server>
weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:249)
at weblogic.nodemanager.server.NMServerConfig.<init>(NMServerConfig.java:190)
at weblogic.nodemanager.server.NMServer.init(NMServer.java:182)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
Caused by: java.lang.UnsatisfiedLinkError: no nodemanager in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1737)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1029)
at weblogic.nodemanager.util.WindowsProcessControl.<init>(WindowsProcessControl.java:18)
at weblogic.nodemanager.util.ProcessControlFactory.getProcessControl(ProcessControlFactory.java:24)
at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:247)
... 5 more
<30/06/2014 3:55:16 PM> <INFO> <Loading domains file: D:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
<30/06/2014 3:55:16 PM> <SEVERE> <Fatal error in node manager server>
weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:249)
at weblogic.nodemanager.server.NMServerConfig.<init>(NMServerConfig.java:190)
at weblogic.nodemanager.server.NMServer.init(NMServer.java:182)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
Caused by: java.lang.UnsatisfiedLinkError: no nodemanager in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1737)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1029)
at weblogic.nodemanager.util.WindowsProcessControl.<init>(WindowsProcessControl.java:18)
at weblogic.nodemanager.util.ProcessControlFactory.getProcessControl(ProcessControlFactory.java:24)
at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:247)
... 5 more
So the nodemanager that was part of the install kept breaking. I installed WLS a number of times and still no luck, so I manually did the node manage again and all was good!
D:\oracle\Middleware\wlserver_10.3\server\bin>setWLSEnv.cmd
Uninstalled existing nodemanager (using D:\oracle\Middleware\wlserver_10.3\server\bin>uninstallNodeMgrsvc.cmd)
Then installed again.
D:\oracle\Middleware\wlserver_10.3\server\bin>installnodemgrsvc.cmd
The it worked!!! Aarrgghhh
No comments:
Post a Comment