My Oracle Support Banner

The nmConnect() Command Fails with the Following Error "Connection to the NodeManager failed due to 'Connection timed out (Read failed)" (Doc ID 2649639.1)

Last updated on MARCH 23, 2020

Applies to:

Oracle WebLogic Server - Version 12.1.1.0 to 12.2.1.4.0 [Release 12c]
Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.0 to 2.0.6.3.0
Information in this document applies to any platform.

Symptoms

The environment has the following step up

Admin Server running on machine a.domain.com
Managed Server X running on machine x.domain.com
Managed Server Y running on machine y.domain.com

The Remote Node Manager status was showing as INACTIVE in the Weblogic Console > Environment -> Machines -> {machine} >Nodemanager > Monitoring tab.

The Remote Node Managers were running fine on Managed Server X host x.domain.com and Managed Server Y host y.domain.com.

Also the telnet/ping was working fine when done on Node manager hostname and port from Admin Machine.

The nmConnect() command runs works fine were executed from the Managed Server X host x.domain.com and Managed Server Y host y.domain.com.

However, the nmConnect() command fails with the timeout error when executed from Admin Server machine - a.domain.com.

ERROR
-----------------------

 

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
References


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