We wanted a queue scoped to the lifetime of the connection, and scoped to a single jms client, so temporary jms queues are a pretty good fit. When the connection dies, the queue and its contents can be automatically discarded. No ACL needed for the queue. etc. It's essentially a one-way event stream, there are no transactional concerns. Also, the producer will notice when the client disconnects (the temporary queue dies), and can stop sending.
Jim On 10/11/2010 2:53 PM, Ashwin Karpe wrote:
Hi, I am not sure what you are trying to do, but why not have a named queue and a Correlation Id to map requests to responses. This way you do not have to worry about time taken by the overall transaction to complete. Passing around temporary queue names around is highly unusual since by definition, temporary queues do not survive if there are no producers or consumers are around and the queue is empty. Also if the broker goes down, such queues are not re-created. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer& Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com http://fusesource.com Blog: http://opensourceknowledge.blogspot.com http://opensourceknowledge.blogspot.com ---------------------------------------------------------
