My Oracle Support Banner

Starting a Server Shows Node Manager Inactive Weblogic.nodemanager.NMConnectException when Machine is Set to localhost (Doc ID 1680197.1)

Last updated on SEPTEMBER 30, 2020

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Oracle Internet Directory - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.
***Checked for relevance on 30-Sep-2020***

Symptoms

Attempt to start a managed server via WL Console fails and outputs the following messages:

In the WL Console, Node Manager is shown inactive via Environment -> Machines -> {machine} and then select Nodemanager & Monitoring tabs, with the following problem description: weblogic.nodemanager.NMConnectException.

Similar exception occurs if the Hostname and IP are not matched correctly in the DNS.  It is needed to ensure two-way connectivity from both AdminServer and managed server.

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
Cause
Solution


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