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 » Aggregate flows behaviour

Post new topic  Reply to topic Goto page Previous  1, 2
 Aggregate flows behaviour « View previous topic :: View next topic » 
Author Message
nathanw
PostPosted: Thu Mar 02, 2006 1:48 am    Post subject: Reply with quote

Knight

Joined: 14 Jul 2004
Posts: 550

All very strange

any chance of posting code of message flows to check over?
Back to top
View user's profile Send private message MSN Messenger
vennela
PostPosted: Sun Apr 02, 2006 11:10 pm    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Even after putting the runtime fix pack for broker 6, I still have the problem.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
wbintegrator
PostPosted: Wed Sep 27, 2006 11:30 pm    Post subject: Reply with quote

Voyager

Joined: 08 Feb 2006
Posts: 83

I just noticed that nathanw suggested "Pass all" NOT "Set all", don't know if it's still relevan.

Anyway I have some weird thing happening here too, so I'll try the suggested by nathanw. I get old replies for requests just posted when there are some older messages in the system's aggregation queues. I hope it will help my issue too.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Sep 28, 2006 2:59 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY

vennela wrote:
Even after putting the runtime fix pack for broker 6, I still have the problem.


Between the aggregate node and the aggregate request node make sure the compute nodes have message and localEnvironment property set. In the compute node copy inputlocalenvironment to outputlocalenvironment.

On the MQOutput nodes make sure the LocalEnvironment after the node looks like you had only set new messageId and no correlation Id. If need be insert a compute node to adjust the local environment (that is if you requested a new correlId).

Works fine for me. But I am not requesting any new correlId on the fanout.
The fanin flow is then expecting the messages to hit the input node with the correlation id equal to the fan out (localEnvironment) advertised messageId.

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Aggregate flows behaviour
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.