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 » flow fails

Post new topic  Reply to topic
 flow fails « View previous topic :: View next topic » 
Author Message
jgoldberg
PostPosted: Mon Mar 14, 2011 3:37 pm    Post subject: flow fails Reply with quote

Newbie

Joined: 14 Mar 2011
Posts: 9
I am evaluating message broker and am having problems running tests let alone completing development of a flow.

HTTP Input -> MQ Output -> MQ Get -> HTTP Reply

When I go to test it gives a timeout on sending a message to HTTP Input about 50% of the time. The other 50% it says there's a problem with my MQ Get node not having a correlID. I saw some other post about this where they added a compute node so I added one and said

SET OutputRoot.Properties.ReplyIdentifier = InputRoot.MQMD.MsgId;
SET OutputRoot.MQMD.CorrelId = InputRoot.MQMD.MsgId;

HTTP Input -> MQ Output -> Compute -> MQ Get -> HTTP Reply


I setup the debugger. When I add breakpoints and test, the breakpoints are skipped and the flow still fails. What am I missing?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Mar 14, 2011 7:50 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
What you are missing is that the msgId / correlationId generated on the MQOutput node is to be found in the LocalEnvironment
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jgoldberg
PostPosted: Tue Mar 15, 2011 2:29 pm    Post subject: Reply with quote

Newbie

Joined: 14 Mar 2011
Posts: 9
fjb_saper wrote:
What you are missing is that the msgId / correlationId generated on the MQOutput node is to be found in the LocalEnvironment


I'm glad everything is so well documented. Looking at the trace/debugger variables output, I added

SET OutputRoot.Properties.ReplyIdentifier = InputRoot.LocalInputEnvironment.WrittenDestination.MQ.DestinationData.msgId;
SET OutputRoot.MQMD.CorrelId = InputRoot.LocalInputEnvironment.WrittenDestination.MQ.DestinationData.msgId;


to the compute node. My output message, according to the trace/debugger, has only MQMD.Format and no Properties.ReplyIdentifier.
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 » flow fails
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.