Using a temporary queue as a reply queue

JMS can create a temporary queue dynamically for use as a reply queue. You can use this to ensure that a reply message is sent to the appropriate queue point for a cluster bus member.

This temporary JMS queue uses a temporary service integration bus queue. Temporary service integration bus queues have only one queue point, irrespective of the number of messaging engines in the bus member. This queue point is created on the messaging engine to which the creating JMS application is connected.

Figure 1. Temporary queue point on the local messaging engine for the requesting application
A temporary queue point on the requesting application local messaging engine.

Therefore, for a cluster bus member with multiple messaging engines (typically, to provide workload management or scalability), you can use a temporary queue to avoid situations where reply messages are sent to the wrong queue point.

This approach has the following advantages:
This approach has the following disadvantages:
Therefore, it is appropriate to use a temporary queue for a cluster bus member with multiple messaging engines only if it is acceptable to lose the reply messages if the application or system stops. If this approach is not acceptable, the following options allow applications to reconnect and process reply messages:



Related concepts
JMS request and reply messaging with cluster bus members
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jan 30, 2014 9:17:32 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-iseries&topic=cjt0021_
File name: cjt0021_.html