![]()
Contents
Cirrus Link Resources
Cirrus Link Website![]()
Contact Us (Sales/Support)![]()
Forum![]()
Cirrus Link Modules Docs for Ignition 7.9.x![]()
Inductive Resources
Ignition User Manual![]()
Knowledge Base Articles![]()
Inductive University![]()
Forum![]()
It is not uncommon for horizontally scalable/clustered MQTT Servers to not support guaranteed in order delivery of QoS 0 messages and this custom property allows the 're-ordering' of messages that arrive out of order.
MQTT Engine needs to process QoS 0 messages in order based on their sequence number. If MQTT Engine receives a message with an out of order sequence number, the message is buffered and the reorderingTimeout timer is started.
If the expected sequence number does not come in before the reorderingTimeout expires, all buffered data is flushed and a rebirth is requested.
If the expected sequence number does arrive before the reorderingTimeout expires, the data in the buffer is processed until the next expected sequence number message is missing, when the reorderTimeout timer is restarted.