ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » CorrId and Aggregate Request & Reply Nodes

Post new topic  Reply to topic
 CorrId and Aggregate Request & Reply Nodes « View previous topic :: View next topic » 
Author Message
AlexeiSkate
PostPosted: Mon Jul 01, 2002 2:43 pm    Post subject: CorrId and Aggregate Request & Reply Nodes Reply with quote

Centurion

Joined: 10 Apr 2002
Posts: 123

I'm sending an input message through an AggregateRequest node, creating two different request messages from it and then I would like the AggregateReply node to aggregate the two replied messages and the original input message into one message.

For the AggregateRequest section, as soon as the request message is placed in a triggered request queue, an in-house built Adapter is immediately activated to read the request msg from the request queue and put a reply into a response queue.

The problem with my message flow is that the AggregateReply node always send the replies to the Unknown Queue.

I can see from the trace node that the replied message has its CorrId set to zeroes. Does my in-house built Adapter need to set the replied msg CorrId to be the same as the request message msgId before the replied msg is placed in the response queue ? Is the CorrId the value that the AggregateReply node uses to aggregate related messages together ?

This is the original message msgId and CorrId before it goes into the AggregateReply node:
(0x3000000)MsgId = X'c19821333edd4dd386e1c4e3fb2c120f0000000000000000'
(0x3000000)CorrelId = X'c19821333edd4dd386e1c4e3fb2c120f0000000000000000'

This is the replied message msgId and CorrId before it goes into the AggregateReply node:
(0x3000000)MsgId = X'414d51204d454c4c4f4e514d20202020d5c0203d12e00100'
(0x3000000)CorrelId = X'000000000000000000000000000000000000000000000000'


thanks,
Alex
Back to top
View user's profile Send private message
devans
PostPosted: Mon Jul 01, 2002 11:32 pm    Post subject: Reply with quote

Apprentice

Joined: 18 Mar 2002
Posts: 43

Alex,
You are correct. You must adhere to the request/reply rules for the underlying transport. In the MQ case, this means that you have to copy the MsgId of the request into the CorrelId of the reply before giving the message to the AggregateReply node.
Back to top
View user's profile Send private message
AlexeiSkate
PostPosted: Tue Jul 02, 2002 2:55 pm    Post subject: Reply with quote

Centurion

Joined: 10 Apr 2002
Posts: 123

Thanks.

I got the Adapter person to modify his code so that the Adapter can assign the CorrId of the reply msg to be the same as the msg id of the request msg, and my Aggregate reply and request nodes appear to be working as expected now.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » CorrId and Aggregate Request & Reply Nodes
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.