Date of First Response: 2009-10-14 04:02:33 Help Desk Ticket Reference: https://support.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId=352029 project_key: SOA When running SOA-P in a clustered UDDI setup, a request may be routed according to three load balance algorithms (AFAIK). * First Available * Round Robin * Random Robin There's no balancer that takes into account that a user might not want the requests to get balanced between the instances in the cluster (since that makes it hard to debug in the event of a failure) This feature request is for a load balance policy for the service invoker that prefers the local instance over other remote instances to avoid having the request jumping between instances.
This is not easy to achieve through a load balancer policy, it would require a new registry interceptor.
I had thought that InVM was the top priority - stay inside the current JVM when possible.
It is if they choose to use it ,but this is for when they want the additional guarantees that a transport such as JMS provides.
Approved for SOA 4.3 CP03, but only if resolved by Due Date.
Link: Added: This issue depends JBESB-3197
Did not make the cut
Draft text for Known Issues section of the Release Notes: https://jira.jboss.org/jira/browse/JBESB-3197 Currently, there is no service invoker load-balancing policy that prefers local end-point references. This would be of use if users do not want requests to be balanced between different instances in the clutter, as the latter makes debugging harder in the event of a failure. There is no work-around for this lack of functionality.
Link: Added: This issue related SOA-2214
See linked issue for registry interceptor addressing this.