| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AggregateReply - Msg going to unknown terminal |
« View previous topic :: View next topic » |
| Author |
Message
|
| ajomillar |
 Posted: Thu Sep 02, 2004 10:10 pm Post subject: AggregateReply - Msg going to unknown terminal |
 |
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
WMQI v2.1 CSD6 on Win2000
MQSeries v5.3 CSD5
Got a problem with messages going to the unknown terminal in the AggregateReply node. The reply message originates from an adapter and is sent to the AggregateReply node. The message immediately goes to the "unknown" terminal. The "Designing Solutions on WMQI" RedBook defines the Unknown terminal which "routes messages when they can not be identified as valid reply messages." If I look at the message itself, how do I know if it is a "valid reply message." Check the CorrelId? Is there some other elements in a message that is required to make it valid? Need help with this since I'm baffled. |
|
| Back to top |
|
 |
| shanson |
| Posted: Fri Sep 03, 2004 4:19 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
Two likely causes:
a) The adapter is not copying the request MQMD msgid to the reply MQMD correlid. The aggregate reply node relies on this being done. What is the adapter, exactly?
b) You had a timeout on the aggregation which had popped - resulting in a partial aggregated reply being sent down the out terminal, and any subsequently received fan-in replies being routed to the unknown terminal. |
|
| Back to top |
|
|
| ajomillar |
| Posted: Fri Sep 03, 2004 5:50 am Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
| Quote: |
| a) The adapter is not copying the request MQMD msgid to the reply MQMD correlid. The aggregate reply node relies on this being done. What is the adapter, exactly? |
WBI PeopleSoft Adapter
In debugger, we see the request Msg Id and reply Correl Id do not match. However, earlier, a teammate showed the correl id in the RFH2 header and how a Compute node was setting the OutputRoot.MQMD.CorrelId = CAST(UPPER(InputRoot.MQRFH2.usr.CorrelationID) AS BLOB). Before that, he was using
| Code: |
| SET OutputRoot.MQMD.CorrelId = InputRoot.MQMD.MsgId; |
This Compute node comes before the AggReply node. His reason: the adapter wasn't setting the CorrelId in the correct place, so he was trying to set this value before AggReply got it. Make sense? |
|
| Back to top |
|
|
| shanson |
| Posted: Fri Sep 03, 2004 6:18 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
First check the fan-out MQ message MQMD to ensure that the msgid is set and that it also says to copy msgid to correlid. If that's ok then it sounds like the adapter is at fault. But I am no WBI adapter expert...
I believe the id that the aggregate reply node thinks it is using is saved in the environment somewhere as ReplyIdentifier? You should check this value. |
|
| 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
|
|
|
|
