WebLogic Server: t3s calls to Cluster Not Load Balancing When One Of the Cluster Member Server is Restarted
Last updated on NOVEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version 10.3 and later
Information in this document applies to any platform.
In a Cluster of 2 or more servers and when one of the members of it have been restarted, all the t3s calls made to cluster will only gets routed to first managed server and not the one which was restarted. The same issue is not seen when using t3 protocol.
Presentation layer --> Business layer (In cluster)
Application .war file (presentation layer) deployed on to AdminServer (front server) and application .ear(business layer) deployed onto two managed server in backend.
When the request is made to backend server, the request routed in round robin to both the backend managed servers. If one of the managed servers is shutdown and if its restarted to join the cluster, then no request will be served. All request land onto other managed server only.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms