| Author |
Message |
 Topic: IMPORTANt!! UNSOLICITED and BAGGREGATE |
devans
Replies: 5
Views: 4439
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 30, 2002 6:52 am Subject: IMPORTANt!! UNSOLICITED and BAGGREGATE |
| I suggest that you try and isolate your problem and contact your IBM Support Centre. I've personally seen dozens of solutions sucessfully using Aggregate nodes. This forum isn't really the best place ... |
| Topic: IMPORTANt!! UNSOLICITED and BAGGREGATE |
devans
Replies: 5
Views: 4439
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 30, 2002 12:57 am Subject: IMPORTANt!! UNSOLICITED and BAGGREGATE |
| What you are describing is not a bug, it is a problem with your flow design. Your fan-out flow should be transactional. If you subsequently have an error in your fan-out flow, then an exception will b ... |
| Topic: IMPORTANt!! UNSOLICITED and BAGGREGATE |
devans
Replies: 5
Views: 4439
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Oct 29, 2002 4:18 am Subject: IMPORTANt!! UNSOLICITED and BAGGREGATE |
A record will be stored in BAGGREGATE for every request message you send out. They are designed to be removed when the replies have come back and the aggregated reply message has been processed.
I ... |
| Topic: Aggregation & DistributionList |
devans
Replies: 9
Views: 5648
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 23, 2002 5:55 am Subject: Aggregation & DistributionList |
I think what you're asking is how do you preserve information such as MsgId and ReplyToQ and suchlike across an aggregation.
The recommendation is that you add an extra arm to your fan-out. In this ... |
| Topic: Problems with Aggregate Reply timeout? |
devans
Replies: 2
Views: 2513
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 23, 2002 3:32 am Subject: Problems with Aggregate Reply timeout? |
Vicky,
3 seconds does mean 3 seconds - give or take a few milliseconds for the OS to swap processes in and whatnot.
Is there anything in your event log complaining about any errors?
My best g ... |
| Topic: Aggregation |
devans
Replies: 14
Views: 10425
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Oct 22, 2002 1:30 am Subject: Aggregation |
| Well, you want everything to be in a transaction, and there are a couple of ways to do it. The safest way is to set your input nodes to transaction=yes because he's the guy who's going to begin and co ... |
| Topic: Aggregation |
devans
Replies: 14
Views: 10425
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Oct 18, 2002 2:01 am Subject: Aggregation |
It sounds like your fan-out isn't transactional or you're sending your request messages with your MQOutput node out of syncpoint.
Trust me about the control message. I wrote these nodes. |
| Topic: Aggregation |
devans
Replies: 14
Views: 10425
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 17, 2002 3:16 am Subject: Aggregation |
| The control message arriving after the reply message will not cause the reply message to be considered "unknown". A reply is only an early reply if it arrives before the DB INSERT performed by the Agg ... |
| Topic: Aggregation |
devans
Replies: 14
Views: 10425
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 17, 2002 12:50 am Subject: Aggregation |
| If your flows are transactional (which they ought to be for aggregation), set the "Unknown timeout" on the AggregateReply node to 0. The value that you set the "Timeout" value on the AggregateControl ... |
| Topic: performance/tread/UOW question |
devans
Replies: 1
Views: 1987
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Oct 11, 2002 4:09 am Subject: performance/tread/UOW question |
| Each input node has at least one thread, so all three flows would operate in the same way regarding scalability, UOWs etc. The only thing worth considering is how easy it is to maintain and correct yo ... |
| Topic: Is the Environment structure thread safe? |
devans
Replies: 2
Views: 2347
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Oct 11, 2002 1:27 am Subject: Is the Environment structure thread safe? |
| A new Environment is created for every message read from an MQInput node. It is not a cross thread storage area. It is thread safe, because only one thread can see it! To store information between thr ... |
| Topic: Aggregation & DistributionList |
devans
Replies: 9
Views: 5648
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 10, 2002 7:12 am Subject: Aggregation & DistributionList |
| The CorrelId has no relevance on the fan-out side (where the AggregateRequest node is). There's nothing to correlate against yet. |
| Topic: Aggregation & DistributionList |
devans
Replies: 9
Views: 5648
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 10, 2002 3:22 am Subject: Aggregation & DistributionList |
| You mentioned that the CorrelId of the 1st and 2nd unknown reply is the same. They shouldn't be the same, because they are merely copies of a MsgId, and every MsgId should be unique. If your CorrelId ... |
| Topic: Aggregation & DistributionList |
devans
Replies: 9
Views: 5648
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 10, 2002 3:17 am Subject: Aggregation & DistributionList |
The fact that the control message isn't arriving in a timely manner isn't of significance here.
May I make a couple of suggestions. Setting the "Unknown timeout" attribute is only relevant if your ... |
| Topic: Aggregation & DistributionList |
devans
Replies: 9
Views: 5648
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 09, 2002 11:13 pm Subject: Aggregation & DistributionList |
| You should be able to use a DestinationList. You haven't provided the full error listing, but it looks like the error is happening in the AggregateReply node, and that it couldn't identify your reply ... |
