WebLogic - DNS/IP Caching Issue With T3 connections.
(Doc ID 1293271.1)
Last updated on SEPTEMBER 28, 2020
Applies to:Oracle WebLogic Server - Version 10.0 and later
Information in this document applies to any platform.
We have a Java client connecting to WebLogic resources using hostname of Weblogic instance for eg: t3://<hostname>:<port no>. If there is change in the underlying IP address to which hostname is resolving to, T3 connections opened to WebLogic JVM instance using hostname still are connecting to old IP address to which hostname was mapping.
Please note there is no change to hostname to which client is connecting to over T3 protocol; only the underlying IP address to which the hostname is resolving has changed.
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