Ensuring that remote EJB client requests stick to the same server instance as the initial context.
(Doc ID 1080300.1)
Last updated on AUGUST 26, 2020
Applies to:Oracle WebLogic Server - Version 9.2 to 10.3.2
Oracle WebLogic Server - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 12c]
Information in this document applies to any platform.
***Checked for relevance on 19-Jan-2013***
You may find that a remote home interface sometimes points to one server instance or another, but not necessarily to the server instance that the EJB client connected to. Since load balancing within a cluster is often desirable to prevent overloading a server, this behavior is how the EJB client works by default. Yet, there may be a reason for the EJB client to always use the EJB remote interface that is running in the same server instance that the client connected to. For example, maybe there is local content on the managed server instance that the client wants.
You will observe two scenarios trying to configure the EJB client to work the way described above. One scenario is that calls to managed servers say <SERVER_1> and <SERVER_2> always go to the EJB in either <SERVER_1> or <SERVER_2>. The other scenario is that calls alternate between one and the other EJB. In other words, load balancing is taking place.
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