Integration Server 10.5 | JMS Client Development Guide | Consuming JMS Messages Concurrently in a Load-Balanced Fashion | Consuming JMS Messages Concurrently from the webMethods Broker
 
Consuming JMS Messages Concurrently from the webMethods Broker
webMethods Broker supports the following load-balancing behavior for JMS destinations.
*Queues. Multiple clients can connect to and receive messages from the same queue if the queue is configured to share state and all the clients use the same client ID.
*Topics. Multiple clients can consume messages in a load-balanced fashion if the clients are connecting to a durable subscriber, state sharing is enabled for the durable subscriber, and all the clients use the same client ID.
Note:
Non-durable subscribers (i.e., JMS triggers that subscribe to topics but do not specify a durable subscriber) cannot receive messages in a load-balanced fashion. A JMS trigger using a non-durable subscriber will process duplicates. Therefore, make sure to set Max execution threads to 1 when setting message processing properties for a JMS trigger that specifies a non-durable subscriber. This behavior may vary with other JMS providers. For more information about configuring message processing, see webMethods Service Development Help.
Note:webMethods Broker is deprecated.