Asynchronous listeners , selectors using messageId

Question

Hi,
Could anyone please advise on a recommended way to register an asynchronous message listener, using a message selector that relies on message id ?
I'm having a race condition, because message ID is only known after you've sent it; by that time, it's too late to register the listener since it may miss the reply.
Some tutorials suggest call connection.start() only after listener is registered, but due to performance reasons I'd rather have a single connection, started when application is started up.
Code example:
// Global, single connection, started on application startup (can't
// affort to re-open and re-start on each request).
QueueConnection con= ...
con.start();
// On request:
QueueSession s = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
Queue queue= s.createQueue...
QueueSender sender = s.createSender();
Message msg=session.createTextMessage(); // jmsMsgId is null
sender.send(msg);  // now jmsMsgId is set
// -- Race condition time: reply may come before listener is registered
String selector="JMSCorrelationID=' + msg.getJmsMessageId() + "'";
QueueReceiver receiver = s.createReceiver(queue, selector);
receiver.setMessageListener( myListener);Thank you very much in advance :)
(A copy of this was also sent to the javaranch forum)

Answer 1

i meant:
QueueConnection con= ...
QueueSession s = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
Queue queue= s.createQueue...
QueueSender sender = s.createSender();
QueueSession rcvSess = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
con.start();of course - in your example you can not create the receiver before the sending of the message, sorry for the misunderstanding, but setting up of the receiving session alone before actually sending can save time.
actually, i would probably set up the application differently.
i can't think of a real-world situation where what you are doing makes sense. you are practically creating a receiver + listener for one message only.
additionally, you create the receiver after the message is sent, and it is in the same application (because otherwise - how do you tell the other side what's the message id? if you can tell the other side what's the message id - you can just as well send it the message).
i wouldn't use a selector the way you did. i don't think you should use the JMSMessageId. If you must set something like this up - try using a property on the message that you'd set to a pre-known value, and use the selector with that.
if you want to elaborate on the problem you're trying to solve, i might be able to give a better answer..
nimo.