| Author |
Message
|
| raj2176 |
 Posted: Tue Mar 27, 2012 11:45 am Post subject: Message Flow Aggregation |
 |
|
Newbie
Joined: 27 Mar 2012
Posts: 3
|
Hi,
I have message flows using aggregation with different names deployed on seperate execution groups but the same broker. I am getting weird result each time.
It is mentioned in the documentation also that using two fan-in flows within the same broker will cause this issue.
Is there a work around for this one?
I am using WMB6.1 on AIX 5.3
Appreicate your reply.
Thanks |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Mar 27, 2012 12:15 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Where is it mentioned in the documentation? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 27, 2012 12:19 pm Post subject: Re: Message Flow Aggregation |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| raj2176 wrote: |
| It is mentioned in the documentation also that using two fan-in flows within the same broker will cause this issue. |
Isn't it two fan-in flows with the same Aggregation control name on different execution groups that's the problem scenario? 
| raj2176 wrote: |
| Is there a work around for this one? |
Upgrade to WMBv7 & use separate WMQ queues to store the state for each aggregation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 27, 2012 12:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Where is it mentioned in the documentation? |
I think the OP means this:
| Quote: |
| Do not deploy a fan-in flow to multiple execution groups on the same broker; results are unpredictable |
Which IMHO doesn't mean exactly what the OP thinks it means.
I'd suspect the OP's flow configuration first.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| raj2176 |
| Posted: Tue Mar 27, 2012 12:22 pm Post subject: |
|
|
Newbie
Joined: 27 Mar 2012
Posts: 3
|
| mqjeff wrote: |
| Where is it mentioned in the documentation? |
Associating fan-out and fan-in aggregation flows
The Aggregate Name must be contextually unique within a broker. You can have only one AggregateControl node and one AggregateReply node with a particular Aggregate Name, although you can have more than one AggregateControl node with the same Aggregate Name, see Using multiple AggregateControl nodes. Do not deploy a fan-in flow to multiple execution groups on the same broker; results are unpredictable. |
|
| Back to top |
|
|
| saurabh867 |
| Posted: Thu Mar 29, 2012 2:13 am Post subject: Message Flow Aggregation |
|
|
Voyager
Joined: 13 Jun 2010
Posts: 78
|
| The line is correct as it says do not deploy a fan-in flow to multiple e.g. It essentially means that you should not deploy fan-in flows to multiple e.g having same aggregation names though you can deploy the fan-in flows having different Aggregation names to same or different e.g. |
|
| Back to top |
|
|
| raj2176 |
| Posted: Thu Mar 29, 2012 9:36 am Post subject: |
|
|
Newbie
Joined: 27 Mar 2012
Posts: 3
|
| Thank you everyone.. appreicate your input. |
|
| Back to top |
|
|
|
|
