Open edburns opened 3 years ago
Johnny Shum 2 minutes ago @Edward Burns It depends on the nature of the conversation. If you get a client and repeatedly make request, it will go to the same server. After you dispose it and recreate another client, it repeats the same behavior. So, it depends on how many ejb client do you have and how long is the conversation. Is there any reason, you are not using stateless ejb ? https://docs.oracle.com/middleware/1213/wls/CLUST/best.htm#CLUST514 Also, there is a settings for load balancing ejb home in the weblogic-ejb.xml descriptor. https://docs.oracle.com/cd/E24329_01/web.1211/e24973/ejb_jar_ref.htm#EJBPG582 Check on stateful-session-descriptor, home-load-algorithm Once a client is obtained, it will stick to it’s instance on a particular server and maintain the conversation until it ends or failed over. Also, there is a settings in the weblogic-ejb.xml docs.oracle.comdocs.oracle.com Clustering Best Practices This chapter recommends design and deployment practices that maximize the scalability, reliability, and performance of applications hosted by a cluster in WebLogic Server 12. docs.oracle.comdocs.oracle.com B weblogic-ejb-jar.xml Deployment Descriptor Reference The following sections describe the EJB 2.1 elements in the weblogic-ejb-jar.xml file, the WebLogic-specific XML Schema-based (XSD) deployment descriptor file.
Hello team, We have a stateful EJB request load balancing issue, the EJB clients in cluster1/domain2 connect EJB servers in squada-n1/domain1 using clusterIP service (e.g t3://sample-domain1-cluster-squada-n1.sample-domain1-ns.svc.cluster.local:9011), we found most of the request were sent to EJB server 1, why not sent to other servers? Attach the snapshot of thread in different managed servers. Please let me know if you need more information.