Yup - request/reply with temp queues is a good model. With ActiveMQ, it is
important to reuse temp destinations, so choose the right model:
GOOD
- create connection
- create temp destination
- repeat
- send request with reply-to = temp destination
- receive response
- delete temp destination (closing the connection is sufficient)
- shutdown
NOT GOOD
- create connection
- repeat
- create temp destination
- send request with reply-to = temp destination
- receive response
- delete temp destination
- shutdown
The latter is especially troublesome over a network of brokers.
BTW, correlation IDs can be used with a common queue, but try to avoid that
- the overhead of selectors is generally a bad thing, and message flow
problems become harder to resolve.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Desktop-applications-tp4684858p4684882.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
