Posted: Mon Jun 13, 2011 3:27 am Post subject: Query on working of Aggregate Nodes
Apprentice
Joined: 06 Feb 2007 Posts: 35
Hi,
I was working on aggregate nodes and below are the flow details.
Fan Out flow:
HTTP Input Node -> Compute 1 -> Aggregate Control
Aggregate Control - > Leg 1 -> Compute 2 -> MQOutput(OrigMsg) -> Agg Req
Aggreage Control -> Leg 2 -> MQ Output (BrokerService) -> Agg Req
In Compute1 I am setting SET OutputRoot.MQMD.MsgId = OutputLocalEnvironment.Varaibles.HTTPRequstId; and transforming the request and will be sent to 2 backends based on the message coming in.
Leg1: In MQOutput(OrigMsg) I am setting the following properties in Advanced Tab. Destination Mode =’Queue Name’ Transaction Mode =’Yes’ Persistence Mode =’Automatic’ and Message Context =’Default’
Leg2: In MQOutput(BrokerService) I am setting the following properties in Advanced Tab. Destination Mode =’Destination List’ Transaction Mode =’Yes’ Persistence Mode =’Automatic’ and Message Context =’Default’ and in Request tab I have mentioned the reply to queue name
Fan In flow:
MQInput(OrigMsg) -> Agg Reply
MQ Input (BrokerService) -> Agg Reply
Agg Reply -> Compute3 -> HTTP Reply
In the above MQInputs I have set Transaction Mode as Yes and Order mode as Default with Logical order check box checked.
While testing I am getting following error:
2011-06-13 05:33:14.941085 13480 UserTrace BIP4412I: Corresponding request record not found for the reply message.
An AggregateReply node has received a message at its 'in' terminal. No corresponding record of a request message being sent could be found. See subsequent messages to determine how this situation has been handled.
It is possible that extraneous messages are arriving at the AggregateReply node 'in' terminal. Check your flow to ensure that the only messages arriving here are replies to request messages previously sent out and passed through an AggregateRequest node. It is possible that this message is a valid reply but part of an aggregation which previously timed out. It is possible that this is a reply to a message which has not yet been recorded by an AggregateRequest node. This can happen if request messages are sent outside of transactional control. Adjust your transaction settings to ensure that messages are sent under transactional control.
2011-06-13 05:33:14.941527 13480 UserTrace BIP4413I: Storing unknown message persistently for subsequent processing.
The message has been stored persistently by the AggregateReply node. If it is subsequently discovered to be a valid reply in an aggregation then it will be processed as such at that time. If a number of seconds passes as specified by the 'unknown timeout' attribute, then the message will be propagated to the 'unknown' terminal.
No user action required.
Please provide some suggestion to resolve this issue.
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