Multiple jms clients ..

Question

          Hi,
          I have a JMS queue (non persistent) in WLS 7.0 and I am interested connecting
          multiple consumers to it. The consumers are stand alone java apps siting on a
          different machine.
          Has anybody experienced any problems with such a configuration ?. I am asking
          because I have been told that multiple consumers can cause queue locks etc ?
          Thanks
          Nick
          

Answer 1

          Nick wrote:
          > Hi,
          >
          > I have a JMS queue (non persistent) in WLS 7.0 and I am interested connecting
          > multiple consumers to it. The consumers are stand alone java apps siting on a
          > different machine.
          >
          > Has anybody experienced any problems with such a configuration ?.
          This is normal. In fact most applications have multiple consumers
          on a destination. (For example,
          each MDB instance in an MDB pool is a consumer.)
          > I am asking
          > because I have been told that multiple consumers can cause queue locks etc ?
          I have not heard of a problem here - the consumers do
          not "know" about each-other directly and do not
          effect each-others transactions - they just share the
          same queue. Some JMS vendors may allow some consumers
          to be "starved" of messages at the expense of other
          consumers, but WL JMS specifically avoids this with
          a round-robin fairness algorithm.
          For extensive design and performance tuning information, see the
          JMS Performance Guide white-paper here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          >
          > Thanks
          >
          > Nick
          >