WebLogic When Acting As Client, Takes Too Long To Send The Request And Trying Non-Routable Network
(Doc ID 2205516.1)
Last updated on NOVEMBER 02, 2022
Applies to:Oracle WebLogic Server - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
A WebLogic clustered serves has two network cards. One network card is dedicated for the admin purposes which is routable. Another card is dedicated for Weblogic and application traffic. This network card (and IP) is non-routable and is only accessible via the load balancer outside of the network. This design works fine in normal cases; however when Weblogic is acting as a client i.e. it has to request some services from other servers in order to fulfill the original request, it tries to send the request through the non-routable network first. We have observed this with tcpdump. Once it times out, it will try on routable network and the request will be successful. However from the end user point of view, this request takes more than 2 minutes while it should take only few seconds.
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