On fetching a WSDL from a OSB Cluster (ManagedServer1 ... ManagedServerN) with a load balancer sitting in front and if the endpoint URL gets set to a particular ManagedServer (Host/Port), then you cluster is not load balanced. If the client application caches the WSDL then you are in deep trouble and is not the right behaviour. In order to make it correct, do the following:
Put the LoadBalance (IP/Port) in Weblogic Admin Console at the following location:
Home -> osb_cluster ->Summary of Environment ->Summary of Clusters -> osb_cluster -> configuration -> HTTP sub-tab
Restart the managed servers and try fetching the WSDL and the endpoint service URL should be set to LoadBalancer (IP/Port) and not any of Managed Server (IP/Port). This should be done for every OSB Cluster with a load-balancer in front
4 comments:
Thanks for the tip. I have a question. When I setup a load balancer on the Admin Server, and I load test with the load balancer url, all requests are going to a single node, so I see CPU saturation on node1 where node2 is doing nothing. Should the load balancer distribute requests across both nodes?
Thanks
Yes the load balancer should distribute the requests across the OSB Managed Servers.
Thanks for sharing your info. I really appreciate your efforts and I will be waiting for your further write ups thanks once again.
Hi,
Thanks for the post.i was searching for such type of information. I will try with the solution
Post a Comment