Load balancing and clustered MDBs using a Queue

Question

With the following advice/information from
          http://e-docs.bea.com/wls/docs61/faq/jms.html#252978,
          "One customer had an example where topic MDBs are needed in which there will
          be multiple implementations of the MDBs listening on the same topic. In
          other words, more than one MDB with a different implementation may be
          subscribing to the same topic. The client has no advanced way of knowing how
          many different kinds of MDBs may be listening on the same topic, but it is
          possible for there to be more than one listener, therefore topics, not
          queues. For each kind of MDB listening on the topic, the message is
          delivered exactly once (i.e., the message will be delivered exactly once to
          an instance in each named MDB pool listening on the topic)."
          If I have a set of MDB's scraping Messages from the JMS Queue, what is the
          load-balancing behavior?
          1) Consider a lightly-loaded system, where each MDB has sufficient time to
          process the message before the next one shows up in the queue. Will the same
          MDB get all the messages?
          2) Consider a heavily-loaded system, where each MDB has insufficient time to
          process the message before the next one shows up in the queue. How would you
          characterize the de facto load-balancing behavior? least-loaded?
          

Answer 1

Have you tried the SAP WebDispatcher.  This should acomplish what you want. 
http://help.sap.com/saphelp_nw04/helpdata/en/42/5cfd3b0e59774ee10000000a114084/frameset.htm