Configuring the requestor to consume messages from all queue points simultaneously

By default, a JMS message consumer consumes from only one queue point for the lifetime of the message consumer. Therefore, if the reply queue has more than one queue point, unless the reply message is restricted to one particular queue point, the consumer might not be consuming from the queue point to which the reply is sent, and might not receive the reply message.

However, you can configure the JMS queue used by the message consumer to allow the message consumer to simultaneously consume from all queue points of the identified service integration bus queue, irrespective of which messaging engine the requesting application is connected to.

The JMS queue option for this is Message visibility. If you enable Message visibility (Message gathering), you do not have to restrict the location of the reply message, as the reply message is visible whichever messaging engine the requesting application is connected to (see Related tasks for more details).

In the following figure, a consuming application connects to a messaging engine that has message visibility enabled but no local queue point. The associated queue point consumes messages from all available queue points of a destination and makes them available to the consumer.

Figure 1. Message visibility: messages are consumed from all queue points
This figure is described in the surrounding text.
Advantages:
Disadvantages:
Concept topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 10:04:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=cjt0022_
File name: cjt0024_.html