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 AUGUST 23, 2021

Applies to:

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

Symptoms

The environment has the following setup:

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

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.host.domain and Managed Server Y host y.host.domain.

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.host.domain and Managed Server Y host y.host.domain.

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

Changes

 

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
Changes
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.