Weblogic Admin Console not working due to the IPv6 Mapping on IP address

Weblogic Admin Console not working due to the IPv6 Mapping on IP address

Error:

If there is a problem using IPv6, we will see error messages like these in the server log:

Caused By: java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '[x:x:x:x:x:x:x:x]', port: 'PORT'

At the same time, the following messages are in stdout:

<Notice> <Log Management> <BEA-170019> <The server log file MW-HOME\user_projects\domains\DOMAIN-NAME\servers\SERVER-NAME\logs\SERVER-NAME.log is opened. All server side log events will be written to this file.>

<Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.> <JTAMigrationHandler> Unexpected exception while getting RemoteMigratableServiceCoordinator : javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://[x:x:x:x:x:x:x:x]:PORT: Destination unreachable; nested exception is:

java.net.ConnectException: Connection timed out: connect; No available router to destination] <JTAMigrationHandler> Unexpected exception while getting RemoteMigratableServiceCoordinator : javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://[x:x:x:x:x:x:x:x]:PORT: Destination unreachable; nested exception is:

java.net.ConnectException: Connection timed out: connect; No available router to destination]

 <Warning> <JTA> <BEA-110503> <The migrator (the AdminServer for manual JTA migration policy, or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potential TLOG corruption if TRS of SERVER-NAME has been migrated to backup server and the backup server is accessing the TLOG of SERVER-NAME. More safety can be achieved by setting isStrictOwnershipCheck to [true].>

 <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>

 <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>

java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '[x:x:x:x:x:x:x:x]', port: 'PORT'

  at weblogic.net.http.HttpClient.openServer(HttpClient.java:333)

  at weblogic.net.http.HttpClient.openServer(HttpClient.java:425)

  at weblogic.net.http.HttpClient.New(HttpClient.java:252)

  at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:189)

  at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler. getDataAsStream(HttpDataTransferHandler.java:75)

  at weblogic.deploy.service.datatransferhandlers. DataHandlerManager$RemoteDataTransferHandler. getDataAsStream(DataHandlerManager.java:153)

  at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload (AppDataUpdate.java:39)

  at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download (DataUpdate.java:57)

  at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareData....

Solution:

1) This error indicates that the OS or network is not handling the IPv6 address correctly, so troubleshooting the problem would require working with the OS or network configuration. Add the host entry in the /etc/hosts file, so the lookup can be faster. 

2) We can disable IPv6 by configuring the URLs (here the admin server URL) with an IPv4 address, or by providing this JVM startup argumentSet "-Djava.net.preferIPv4Stack=true" in the JVM arguments, so that the client or host can prefer IPv4 addresses instead of IPv6 to avoid any related issues. 

In setDomainEnv.sh add below

JAVA_OPTIONS=$JAVA_OPTIONS -Djava.net.preferIPv4Stack=true

If you like please follow and comment