Posted: Thu May 06, 2010 9:23 am Post subject: Selecting messages by CorrelationID in an MDB/JMS service
Novice
Joined: 22 Feb 2010 Posts: 10
I am developing a service to be deployed on Websphere that is MQ-enabled. This new service is a replacement for an existing service and has some legacy clients. I am planning to use an MDB with a JMS listener. The problem I have is that there are multiple other services that share the same request and reply queue. The individual services get their service-specific messages from the queue by filtering on the CorrelationID of the incoming request message. Each service has it's own CorrelationID. For the record, the clients and other services on this queue are Windows-based. Changing them is not really an option.
What I'd like to know is how I can configure my MDB and/or JMS listner in Websphere to only take the messages from the queue with my service's specific CorrelationID.
Posted: Fri May 07, 2010 2:40 am Post subject: Re: Selecting messages by CorrelationID in an MDB/JMS servic
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
weskelton wrote:
I am developing a service to be deployed on Websphere that is MQ-enabled. This new service is a replacement for an existing service and has some legacy clients. I am planning to use an MDB with a JMS listener. The problem I have is that there are multiple other services that share the same request and reply queue. The individual services get their service-specific messages from the queue by filtering on the CorrelationID of the incoming request message. Each service has it's own CorrelationID. For the record, the clients and other services on this queue are Windows-based. Changing them is not really an option.
What I'd like to know is how I can configure my MDB and/or JMS listner in Websphere to only take the messages from the queue with my service's specific CorrelationID.
Thanks
Look @ the JMS request reply sample. It is spelled out in detail.
Be aware that up to V6 the handling is done client side and if you need performance you will HAVE TO use the provider method (correlId=ID:hexvalue).
Have fun _________________ MQ & Broker admin
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum