Last updated on FEBRUARY 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.3 and later
Information in this document applies to any platform.
Customer has an Oracle Fusion Middleware (FMW) 11g cluster configured WebLogic Server (WLS) with 1 admin server and 4 managed servers. Cluster runs on 2 machines.
First machine runs Node Manager, Admin Server and 2 managed servers. Second machine runs Node Manager and remaining 2 managed servers.
Each machine has 2 IP addresses, but only one is visible to the other machine. The listen address for all servers is set to blank so that all addresses are listened for by WLS.
Communication between managed servers on the second machine and admin server is broken in some way because it uses the IP address which is not visible. Deployment artifacts do not propagate to the second machine and both managed servers appear to be down in Node Manager.
There is the following error in the adminserver.log:
That's why later on when a managed server from the other machine tries to connect to admin server it tries to use the wrong IP address and gets the exception "No route to host."
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