MQSeries.net :: View topic - MDB getJMSDestination() NULL when source is MQ

jdwelsh · Posted: Tue Aug 22, 2006 1:19 pm Post subject:

I have a message-driven bean that is configured to receive messages on many different queues. Within the MDB, I determine the Queue on which the message was delivered, and use the name of the queue to identify the source of the message and process it properly. The assumption is that the name of the Queue uniquely identifies the source application. The following is a a simple code sample:

public void onMessage(Message msg) {
...
Queue queue = (Queue) msg.getJMSDestination();
...
}

When I test this out by putting the message on the Queue via JMS, this works properly. However, when the message is put in the Queue via MQ, getJMSDestination() returns NULL.

As I did some research, I found that there is a MQRFH2 field "jms.Dst" that seems to correspond to JMSDestination. The MQ experts I've talked with tell me that the generated message does not necessarily have MQRFH2 so using this is not a possibility.

So, my question is this - is there any standard for providing the name of the Queue to a target system? Someone suggested to use MQMD field ReplyToQ, but a colleague told me this is not a standard approach and may face some opposition from MQ guys. I'd prefer not to embed the name of the queue in the message itself, but that is my last resort option.

I'm trying to design an open interface that will be accessible to many clients, and I certainly don't want to add requirements that may face opposition. At the same time, I don't want to client to have to identify themselves other than by putting the message on the correct queue.

Thanks in advance