How are compound messages built by the AggregateReply node in WebSphere Message Broker (WMB)?
Compound message building on the AggregateReply node can be triggered in three cases:
- When the AggregateControl node timeout expires. The timeout expiration triggers a known timeout thread on which all the reply messages that are available on the SYSTEM.BROKER.AGGR.REPLY queue and replies that have reached the SYSTEM.BROKER.AGGR.UNKNOWN queue are appended under the AggregateReplyBody of the compound message. If no reply message is available on the SYSTEM.BROKER.AGGR.REPLY or SYSTEM.BROKER.AGGR.UNKNOWN queues, the AggregateReply node propagates a message with an empty Properties and AggregateReplyBody, as nothing has been received with which to build a compound message.
- When an unknown message times out, based on the Unknown Message Timeout property that is set on the AggregateReply node. This timeout collates the corresponding request messages on the SYSTEM.BROKER.AGGR.REQUEST queue and any replies that have reached the SYSTEM.BROKER.AGGR.REPLY queue to build a compound message.
- When the last reply arrives on the AggregateReply node. The last reply is appended at the end of the AggregateReplyBody.
WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI