Friday, July 7, 2017

Weblogic 11G Destination unreachable;

I have a local clustered environment with an Admin server and two nodes node1, and node2.
I am getting following while starting the node1 and node2. The error is basically complaining about the destination not reachable when it tries to connect the Admin server.

It shows the destination as follows:

[fd56:801a:cd17:0:39c0:fd3e:4d90:1ce]:7001

Here is the full stacktrace:

<Jul 7, 2017 10:57:08 AM CDT> <Warning> <JMX> <BEA-149509> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://[fd56:801a:cd17:0:39c0:fd3e:4d90:1ce]:7001/jndi/weblogic.management.mbeanservers.domainruntime.
java.io.IOException
        at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
        at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
        at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:369)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
        at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)
        Truncated. see log file for complete stacktrace
Caused By: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://[fd56:801a:cd17:0:39c0:fd3e:4d90:1ce]:7001: Destination unreachable; nested exception is:

Fix in my case : 

For me setting the Listen address localhost resolved the issue.
Go to weblogic console and check the AdminServer Listen Address. I set it to localhost since I am working on my local but this can be an IP if you are working on remote environment.


No comments:

Post a Comment