Question

After Stopping Node Manager we cannot start it again - IFS APP 10

  • 29 July 2021
  • 1 reply
  • 796 views

Userlevel 7
Badge +18

After stopping the Node Manager using MWS-SVR.cmd it will not restart.

Please see snippet from the Node Manager Log file:

 

<Jul 29, 2021 9:14:47 PM BST> <INFO> <Loading domains file: F:\IFS\IFSMWS\IFSR\wls_domain\IFSR\nodemanager\nodemanager.domains>
<Jul 29, 2021 9:14:47 PM BST> <INFO> <Loading identity key store: FileName=F:/IFS/IFSMWS/IFSR/instance/IFSR/security/truststores/ifs_mws.jks, Type=jks, PassPhraseUsed=true>
<Jul 29, 2021 9:14:47 PM BST> <INFO> <Loaded NodeManager configuration properties from 'F:\IFS\IFSMWS\IFSR\wls_domain\IFSR\nodemanager\nodemanager.properties'>
<Jul 29, 2021 9:14:47 PM BST> <INFO> <12.2.1.3.0>
<Jul 29, 2021 9:14:47 PM BST> <INFO> <IFSR> <AdminServer> <Startup configuration properties loaded from "F:\IFS\IFSMWS\IFSR\wls_domain\IFSR\servers\AdminServer\data\nodemanager\startup.properties">
<Jul 29, 2021 9:14:47 PM BST> <INFO> <IFSR> <AdminServer> <Resume monitoring of active server process (pid = 7832)>
<Jul 29, 2021 9:14:47 PM BST> <INFO> <IFSR> <AdminServer> < Initializing ServerMonitor for weblogic.nodemanager.server.ServerManager@38afe297 : with config : weblogic.nodemanager.common.StartupConfig@2df3b89c>
<Jul 29, 2021 9:14:47 PM BST> <INFO> <IFSR> <IntServer1> <Startup configuration properties loaded from "F:\IFS\IFSMWS\IFSR\wls_domain\IFSR\servers\IntServer1\data\nodemanager\startup.properties">
<Jul 29, 2021 9:14:47 PM BST> <INFO> <IFSR> <MainServer1> <Startup configuration properties loaded from "F:\IFS\IFSMWS\IFSR\wls_domain\IFSR\servers\MainServer1\data\nodemanager\startup.properties">
<Jul 29, 2021 9:14:47 PM BST> <INFO> <Server Implementation Class: weblogic.nodemanager.server.NMServer$ClassicServer.>
<Jul 29, 2021 9:14:47 PM BST> <SEVERE> <Fatal error in NodeManager server>
java.io.IOException: The server is unable to create a server socket for listening. The address testapp01 might be incorrect or another process is using port 61093: java.net.BindException: Address already in use: JVM_Bind
    at weblogic.nodemanager.server.NMServer$ClassicServer.start(NMServer.java:780)
    at weblogic.nodemanager.server.NMServer.start(NMServer.java:362)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:591)
    at weblogic.NodeManager.main(NodeManager.java:31)
Caused by: java.net.BindException: Address already in use: JVM_Bind
    at java.net.DualStackPlainSocketImpl.bind0(Native Method)
    at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:102)
    at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:513)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:180)
    at java.net.ServerSocket.bind(ServerSocket.java:375)
    at java.net.ServerSocket.<init>(ServerSocket.java:237)
    at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:181)
    at sun.security.ssl.SSLServerSocketImpl.<init>(SSLServerSocketImpl.java:78)
    at sun.security.ssl.SSLServerSocketFactoryImpl.createServerSocket(SSLServerSocketFactoryImpl.java:87)
    at weblogic.nodemanager.server.SSLListener.privilegedInit(SSLListener.java:102)
    at weblogic.nodemanager.server.SSLListener.access$000(SSLListener.java:35)
    at weblogic.nodemanager.server.SSLListener$1.run(SSLListener.java:65)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:62)
    at weblogic.nodemanager.server.NMServer$ClassicServer.start(NMServer.java:778)
    ... 3 more

 

Can anyone please advise.

Thank you for looking.


This topic has been closed for comments

1 reply

Userlevel 5
Badge +12

Hello @johnw66 

Do you have another middleware instance also configured in this host or have an instance installation done incompletely and left as is?

Seems like one of your ports (61093) is already listening to another process hence target mws server process can not connect to it.

Have you tried finding that process id and killing it (complete server reboot also will work if it’s not a startup type=automatic enabled windows service)