Hide Forgot
Date of First Response: 2008-01-15 04:45:24 project_key: SOA Platform JIRA for project JIRA: JBESB-1344 Few gateways do not use Service Invoker. It means that they do not provide load balancing facility right now. This needs to be documented and fixed later. The gateways are JmsGatewayListener.java HibernateInterceptor.java SqlTableGatewayListener.java Loadbalancing is only performed when a raw (native) message is transformed into an ESBMessage. For example, in the quickstarts, sending a message to the ESB through the JMS-Gateway with the SendJMSMessage class will not be loadbalanced. Messages sent straight to the ESB listener, and not through a gateway, by the SendEsbMessage class will be loadbalanced. If you deploy a gateway on multiple ESBs, and they listen to the same clustered queue, then they will share the load through JBM clustering, but there is no failover to another type of EPR.
Link: Added: This issue depends JBESB-1344
Link: Added: This issue depends JBESB-1347
Link: Removed: This issue depends JBESB-1344
==Proposed for Release Notes== In this release the following gateways do not use the ServiceInvoker, and therefore do not provide load balancing: * JmsGatewayListener.java * HibernateInterceptor.java * SqlTableGatewayListener.java Load balancing is performed when a raw message is transformed into an ESBMessage, or when an ESBMessage is sent to an ESB listener. Be aware that a raw (non-ESB) message sent through one of the above three gateways will not be load balanced. When one of these gateways is deployed on multiple ESBs that listen to the same clustered queue they will share the load through JBM clustering, but there is no failover to another type of EPR. These gateways will have load balancing enabled in a future release.
Fine. The ESB docs carry a similar disclaimer.
http://engineering.redhat.com/docbot/en-US/JBoss_SOA_Platform/4.2/html-single/SOA_Release_Notes/#id2804736
Verified in the release notes in RC1.