You can use two properties of the aggregation nodes to set timeout values for aggregated message processing.
Before you start:
To complete this task, you must have completed the following tasks:
There are two situations that might require the use of timeouts:
If the timeout interval passes without all the replies arriving, the replies that have arrived are turned into an aggregated reply message by the corresponding AggregateReply node, and propagated to its timeout terminal. If you choose, you can process this partial response message in the same way as a complete aggregated reply message. If you prefer, you can provide special processing for incomplete aggregated replies.
These situations are most likely to happen if you send the request messages out of syncpoint, and might result in valid replies being sent to the unknown terminal. To reduce the chance of this event:
If the unknown timeout interval expires, and the message is recognized, it is processed. The node also checks to see if this previously unknown message is the last reply needed to make an aggregation complete. If it is, the aggregated reply message is constructed and propagated.
If the unknown timeout interval expires and the message is still not recognized, the message is propagated to the unknown terminal.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac12320_ |