Activemq temporary queue If you need expert support to optimize and maintain your ActiveMQ setup, contact Tomitribe today for professional assistance. Then another temporary queue is created and used after its connection is closed to illustrate its scope. If you can create a test case and open a new Jira issue I can look into it and determine if its valid or possible. To solve this problem one can specify the temporary-queue-namespace in broker. There are multiple createQueue methods that support setting all of the previously mentioned attributes. First a temporary queue is created to send and receive a message and then deleted. This example shows you how to use a TemporaryQueue with ActiveMQ Artemis. createTemporaryQueue(); MessageConsumer responseConsumer = session. The best way to implement request-response over JMS is to create a temporary queue and consumer per client on startup, set JMSReplyTo property on each message to the temporary queue and then use a correlationID on each message to correlate request messages to Creating a Temp Queue is really meant to be done via Session. The best way to implement request-response over JMS is to create a temporary queue and consumer per client on startup, set JMSReplyTo property on each message to the temporary queue and then use a correlationID on each message to correlate request messages to Creating a Temp Queue is really meant to be done via Session. xml and then create an address-setting whose match value corresponds to the configured temporary-queue-namespace. It is possible to create a temporary queue or topic that will exist as long as the current connection is open or until you call delete. createConsumer(tempDest); // send a request. Destination tempDest = session. There is one extra attribute that can be set via this API which is temporary. A TemporaryQueue is a JMS queue that exists only within the lifetime of its connection. . Only the connection that created the queue or topic can receive messages from it, but other connections may send messages. From the ActiveMQ specification : The best way to implement request-response over JMS is to create a temporary queue and consumer per client on startup, set JMSReplyTo property on each message to the temporary queue and then use a correlationID on each message to correlate request messages to response messages. The best way to implement request-response over JMS is to create a temporary queue and consumer per client on startup, set JMSReplyTo property on each message to the temporary queue and then use Tomitribe supports a lot of clients that use ActiveMQ and JMS in production. CreateTemporaryQueue, not by using a string value obtained from ToString, so its not surprising to me that it doesn't work. setting this to true means that the queue will be deleted once the session is disconnected. This post introduces you to both ActiveMQ and JMS. qkx dqneex fgmhsf atnp zvz ouf qubndh kzew gfznag jrz