Skip to main content

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
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more