WebLogic (WLS):Managed Server Fails to Connect to Admin Server When Listening on both Internal and External IPs (multiple network cards)
(Doc ID 943087.1)
Last updated on OCTOBER 29, 2020
Applies to:Oracle WebLogic Server - Version 10.0 to 10.3.2
Information in this document applies to any platform.
The WebLogic Server (WLS) Admin Server is running on two addresses: one is internal and the other is an external address. Trying to start managed servers on remote machine by providing the admin URL and using the external address causes a failure.
During this process, the managed server could not communicate with Admin Server using the external address. Instead it is trying to connect with the internal IP address even if we specify the external IP address.
When WLS servers are created without an explicit listen address, the WLS server listens on all available IP addresses. But it also chooses the DHCP/Virtualized IP as a default network channel when it is available, and all server to server or cluster broadcasts occur on this channel. This causes issues when the virtual bridge or router blocks unicast/multicast traffic and also server to server communication across domains. Multicast/unicast announcements get dropped and the cluster members get dropped and added every minute.
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