| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Aggregation behaving weird |
« View previous topic :: View next topic » |
| Author |
Message
|
| kspranava |
 Posted: Fri Jul 21, 2006 6:38 am Post subject: Aggregation behaving weird |
 |
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Dear Gurus,
I am using aggregation message flow in Broker v6.0.0.1 (Windows 2000 professional and WMQ5.3) where the MQ queues are used in placed of tables to store aggregate messages by the broker.
When I pump in test data (only a few fan out requests), I get the output collated not always. So far I have seen error codes 2034 and 2026 in event viewer and messages get stuck in either SYSTEM.BROKER.AGGR.* queues or routed to DLQ. At times even messages are tied to wrong Aggregate folder names.
Did any one come across such problem?
Thanks,
kspranava |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Jul 21, 2006 7:46 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| kspranava |
| Posted: Fri Jul 21, 2006 8:30 am Post subject: |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi Vennela,
It's interesting; only we two got such strange behaviour or is it others not rising it here? BTW did you get any error codes in event viewer / syslogs?
Broker on its own generates new message id for every request unless we don't select 'Request' option and supply a value for 'Reply To Queue' in MQOutput node preceeding Aggregate Request Node. Otherwise we need to select 'New Message Id'.
Looking forward to IBMers to throw some light.
Thanks,
kspranava. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 21, 2006 9:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
OK here is how I made aggregation work in 6.0 fix pack 1:
On the Fan out set pass all and check new messageId. Before the fan out set correlationId to MQCI_NONE. If the correlationId is set the aggregation does not behave as expected.
I set up an extra branch on the fanout where the serialized input MQMD is passed in CDATA (XML).
This message goes to a flow that just throws it to the reply destination (MQReply node) in this case the aggregation queue. In the aggregation compute node I extract the MQMD (create parse) and thus I have the original reply to destination and correlationId.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
