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 » Aggregation woes after CSD update

Post new topic  Reply to topic
 Aggregation woes after CSD update « View previous topic :: View next topic » 
Author Message
lung
PostPosted: Tue Feb 17, 2004 6:58 pm    Post subject: Aggregation woes after CSD update Reply with quote

Master

Joined: 27 Aug 2002
Posts: 291
Location: Malaysia

I have recently upgraded from CSD03 to CSD05, and am experiencing some pretty weird issues pertaining to aggregation.

I have this flow

Code:

In-> AggCtrl -> Compute -> OutA -> AggReqA -> TraceA
                                     -> OutB -> AggReqB -> TraceB

InA -> AggRpl
InB ->


The flow is pretty simple; After the Compute, I connected two output nodes to its out terminal, thus propagating the message into two. The OutA leads to a flow that switches the CorrelId with the MsgId, and leads to InA. OutB leads to another machine, who will reply to InB (after switching the CorrelId with MsgId as well). Problem is... The reply from InA will always end up as 'unknown' after the AggRpl. What gives? The reply from InB, on the other hand, will always pass through successfully. And there's not even a timeout! It is as if the AggReqA is failing, but I've checked the trace from TraceA and I can see clearly the aggregation values are there!

Why is the broker not recognising AggReqA?

I have even tried setting the timeout values (for both the aggregation and the unknown reply) to 1 whole minute. Same results.

Wut's even more frustrating is... At random times (although rare), both replies will pass through successfully!

Please help.
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
TonyD
PostPosted: Wed Feb 18, 2004 2:28 pm    Post subject: Reply with quote

Knight

Joined: 15 May 2001
Posts: 540
Location: New Zealand

I would set the timeout to, say, 5 minutes, add TraceC between InA and AggRepl, run the flow, and if the InA reply ends up on the Unknown terminal as expected, have a look in the table BAGGREGATE to determine whether the CorrelationId in the InA reply actually matches REPLYID in InA's row (FOLDERNAME). The longer timeout is to ensure that you have time to look at the rows in BAGGREGATE.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Aggregation woes after CSD update
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.