ConnectionFactory - who does the load balancing

Question

          Consider creating a connectionfactory (with server affinity unticked, load balancing
          ticked and using the message delivery policy of round robin) we then go on to
          create a distributed domain targetted at the cluster of two managed server's (managed1
          and managed2)
          If I create a simple java app that put's messages to that distributed destination,
          using the connectionfactory above, who's responsible for doing the load balancing.
          Does the client create the session knowing that the connectionfactory requires
          load balancing and thus takes the responsibility for it, or does the client just
          put a constant stream of JMS messages to the WLS and the connectionfactory class
          takes responsibility for the load balancing
          Who maintain's the delivery state, the client application or WLS (i.e who's job
          is it to look up the last messages queue destination?)
          

Answer 1

Hi Barry,
          A JMS client's produced messages are first delivered to the WL server
          that hosts the client's JMS connection. The JMS connection
          host remains unchanged for the life of the connection.
          Once produced messages arrive on the connection host,
          they are load balanced to their JMS destination.
          For more information I suggest reading the clustering
          sections of the JMS Performance Guide white-paper. You can find
          the white-paper here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          Tom Barnes
          Barry Myles wrote:
          > Consider creating a connectionfactory (with server affinity unticked, load balancing
          > ticked and using the message delivery policy of round robin) we then go on to
          > create a distributed domain targetted at the cluster of two managed server's (managed1
          > and managed2)
          >
          > If I create a simple java app that put's messages to that distributed destination,
          > using the connectionfactory above, who's responsible for doing the load balancing.
          >
          > Does the client create the session knowing that the connectionfactory requires
          > load balancing and thus takes the responsibility for it, or does the client just
          > put a constant stream of JMS messages to the WLS and the connectionfactory class
          > takes responsibility for the load balancing
          >
          > Who maintain's the delivery state, the client application or WLS (i.e who's job
          > is it to look up the last messages queue destination?)
          >
          >
          >
          >