Imported from previous forum
If a SequenceReset message is received, with say NewSeqNo<36>=100, then another message is received with Seq # 99, how should the message be handled?
Our FIX engine (Quickfix) ignores any message below 100 and only begins handling the messages 100 and above. Should it instead reject those messages as Seq Num too low?
[Start Quote from section “Session Protocol > Message Recovery”]
If the incoming message has a sequence number less than expected and the PossDup flag is not set it indicates a serious error and it is strongly recommended that the session be terminated and manual intervention be initiated.
[End Quote]
If a SequenceReset message is received, with say NewSeqNo<36>=100,
then another message is received with Seq # 99, how should the message
be handled?Our FIX engine (Quickfix) ignores any message below 100 and only begins
handling the messages 100 and above. Should it instead reject those
messages as Seq Num too low?
If a SequenceReset message is received, with say NewSeqNo<36>=100,
then another message is received with Seq # 99, how should the message
be handled?Our FIX engine (Quickfix) ignores any message below 100 and only begins
handling the messages 100 and above. Should it instead reject those
messages as Seq Num too low?
Unless your counterparty FIX engine is acting weird, it’s probably sending these messages as a result of a ResendRequest you(r FIX engine) sent(?)
If a SequenceReset message is received, with say NewSeqNo<36>=100,
then another message is received with Seq # 99, how should the message
be handled?Our FIX engine (Quickfix) ignores any message below 100 and only
begins handling the messages 100 and above. Should it instead reject
those messages as Seq Num too low?Unless your counterparty FIX engine is acting weird, it’s probably
sending these messages as a result of a ResendRequest you(r FIX
engine) sent(?)
Yes that is the case. When the initiator connects to my side, it adds 100 to the last sequence #, call it X. My side then sends a resend reqeust for X to 0. The initiator then sends a reset to X+102, then is starts sending application messages starting with X+101. My side ignores the X+101 message and does normal processing for the others X+102 and on.