Hi,
as was said earlier the lifespan of the temporary queue is controlled by
the
ActiveMQ runtime - more specifically the connection that was used to
create
the temporary destination.
If that doesn't suite your need I think you may have an architecture
problem.
Is a temporary queue with it'
Hi
Thanks for the reply.I will explain my workflow
request (publishing) Consuming
*client*-->*activemq*>*service*
<- <-
Reply Reply back to te
You should always use the name provided by JMSReplyTo header. It
shouldn't make a difference which session you're using. Temporary
destination lifecycle (creation, and removal) are tied to the
connection that created it, so you'd have to verify the connection is
still around when you're using the t
