Last updated on MAY 12, 2017
Applies to:Oracle Fusion Middleware - Version 126.96.36.199.0 and later
Oracle HTTP Server - Version 188.8.131.52.0 and later
Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
- This is typically affecting Oracle HTTP Server standalone installations
Goal is to change the Node Manager port and ensure the startComponent script picks up the new value. If multiple domains on the same machine failures will occur if using the same port. Historically, the node management port was changed with nodemanager.properties, but beginning with version 12.1.2, there is an additional step to update the config.xml.
If the Node Manager is restarted after only editing the nodemanager.properties, the startComponent script may give the following error depending on different circumstances:
Error: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Connection refused.
Could not connect to NodeManager. Check that it is running at localhost:5556
Error Starting server ohs1: weblogic.nodemanager.NMException:
Received error message from Node Manager Server: [Server start command for OHS server 'ohs1' failed due to: [Invalid instance ohs1].
Error Starting server ohs1: weblogic.nodemanager.NMException: Received error message from Node Manager Server: [OHS Server 'ohs1' is either already running or in the process of starting/restarting].
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms