EJB Load Balance Not Working. All Remote EJB Calls are Going to One Node On the Cluster
(Doc ID 460088.1)
Last updated on JUNE 02, 2023
Applies to:
Oracle Containers for J2EE - Version 9.0.4.2.0 to 10.1.2.3.0 [Release AS10g to AS10gR2]Information in this document applies to any platform.
Symptoms
Web application invokes an EJB (stateless session beans) in another application,
the EJB requests are not distributed among the two nodes in the cluster.
All requests go to just one node.
These are the initial context properties:
Context.INITIAL_CONTEXT_FACTORY=com.evermind.server.rmi.RMIInitialContextFactory
Context.SECURITY_PRINCIPAL=user
Context.SECURITY_CREDENTIALS=password
dedicated.rmicontext=false
dedicated.connection=true
It was attempted the following urls:
Context.PROVIDER_URL=opmn:ormi://node1server:6003:home/EarFileName
Context.PROVIDER_URL=opmn:ormi://node2server:6003:home/EarFileName
Context.PROVIDER_URL=opmn:ormi://localhost:6003:home/EarFileName
No matter which web application node the EJB request originates from or which URL is used in the
initial context, they all seem to be processed on node1.
.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |