On WebLogic 184.108.40.206 Server Template Listen Address Causes JMX Connectivity Issue On Admin Console
(Doc ID 2299752.1)
Last updated on MARCH 09, 2020
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On WebLogic Server18.104.22.168.0 version, when configuring Dynamic Clusters, and setting a DNS name for Listen Address on Server template, Dynamic Server comes up correctly but Admin Console cannot connect to Managed Server and gives below error:
<The Administration Server was unable to establish JMX Connectivity with the ManagedServerHostName at the JMX Service URL of service:jmx:t3://<ADMINSERVERHOSTNAME>:<PORT>/jndi/weblogic.management.mbeanservers.runtime.>
On each machine, AdminServerHostName has been configured to the IP address of the machine on /etc/hosts.
The very same setup worked fine for customer on WLS 12.1.3, where the machine hostname was used as the address where the Admin Console will make the JMX call to monitor the server health.
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