Use TCP Load-Balancer For WebLogic JMS
(Doc ID 2915687.1)
Last updated on DECEMBER 16, 2022
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The JavaClient request is forwarded to WLS Servers via AWS TCP LoadBalancer. Client (with wlthint3client.jar) is exactly behaving as expected and explained in below documentation
"Initial Context Affinity and Server Affinity for Client Connections" at https://docs.oracle.com/en/middleware/fusion-middleware/weblogic-server/22.214.171.124/clust/load_balancing.html#GUID-710D22ED-A90A-4A69-B3FD-578A6250FF8A
When the client is using the connection factory stub and is routed via that to the same server of the cluster that the client already contacted for doing the JNDI-Lookup, then the TCP-Socket that was already created for the JNDI-Lookup is reused. Call flow is always through the Load Balancer. TCP-Socket will go via the Load-Balancer in between and the client is NOT using the listening address of that server that was given in the stub.
There is a request for enhancement to have a option (argument or setting) that would allow to Change this behavior, so that for creating the connection/consumer/producer always one of the listen addresses of stub is used without re-using the TCP-Socket opened for doing the JNDI-Lookup (which is going via the Load-Balancer). i.e. Once the JNDI lookup happen, is it possible to have client directly
connect backend WLS server and by-pass Load Balancer?
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