-

You might think at first that to implement request-response type operations in JMS that you should create a new consumer with a selector per request; or maybe create a new temporary queue per request.

+

You might think at first that to implement request-response type operations in JMS that you should create a new consumer with a selector per request; or maybe create a new temporary queue per request.

Creating temporary destinations, consumers, producers and connections are all synchronous request-response operations with the broker and so should be avoided for processing each request as it results in lots of chat with the JMS broker.

@@ -289,7 +288,36 @@

The actual class which does this is the MultiplexingRequestor . It may be just using Spring remoting with Lingo is the simplest way of implementing request response - or maybe you could just use Lingo's Requestor interface to keep the JMS semantics.

-

More details here

+

More details here

+ +

Client side

+ +

So the client side creates a consumer on a temporary queue as follows...

+ +

+

// client side
+Destination tempDest = session.createTemporaryQueue();
+MessageConsumer responseConsumer = session.createConsumer(tempDest);
+...
+
+// send a request..
+message.setJMSReplyTo(tempDest)
+message.setJMSCorrelationID(myCorrelationID);
+
+producer.send(message);

+

+ +

Server side

+ +

+

public void onMessage(Message request) {
+
+  Message response = session.createMessage();
+  response.setJMSCorrelationID(request.getJMSCorrelationID())
+
+  producer.send(request.getJMSReplyTo(), response)
+}

+