It's also possible to use temporary destionations for request/reply. Have the requestor create a temporary queue and set that as the JMSReplyTo of the message before sending to the server that will send back the reply. Then the server replies to the JMSReplyTo address on the message.
When using this solution, be careful to avoid creating and destroying temp destinations rapidly. The right way to use a temporary destination in this case is to create one when the requestor creates the JMS connection, then reuse that destination. Selector overhead is a real concern. It has been recommended strongly to me by experts to avoid using selectors as they notably impact overall broker performance. If your architecture works to use a requestor-specific queue (not a temporary queue) then that's a great way to go as it avoids race conditions and other potential issues with temporary destinations. Under the hood, if I understand correctly, Camel uses temporary destinations to implement request/reply with JMS. -- View this message in context: http://activemq.2283324.n4.nabble.com/Request-Response-in-ActiveMQ-tp4675769p4676066.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
