Imported from previous forum
In the “FIX_Transport_1 1.pdf”, under the section “Logon Message NextExpectedMsgSeqNum Processing” it is stated that “Neither side should generate a ResendRequest based on the MsgSeqNum (34) of the incoming Logon message but should expect any gaps to be filled automatically…”.
But at the same just above this section in the “Response by Message Type” table, for Logon message it is stated that “Must always be the first message transmitted. Authenticate and accept the connection. After sending the Logon confirmation back, send a ResendRequest if a message gap was detected in the Logon sequence number.”
As these two statements are contradictory, I am a bit confused about handling a Logon Request with a greater than expected sequence number.
In this case should:
a) A ResendRequest be sent to the counterparty or
b) An auto resynchronization should be expected from the client, after sending Logon Response with the NextExpectedMsgSeqNum (Tag 789)?
Will there be any change in handling the sequence number (in Tag 34), received in the Logon message?
Thanks in Advance,
Vinay M
It just depends on individual implementations which could be exchange specific as well as bilateral agreement between counterparties. The FIXT.1.1 specification seems to encourage monitoring of the value sent by the counterparty in Tag 789 with our Tag 34 so that we could proactively detect a sequence gap and take action accordingly without waiting to be prompted for an explicit resend request issued by the counterparty which will be sure to follow once it recieves the message and sees that there is a gap.
The best bet is to issue a resend request anyway (after a pause perhaps) so that you are covered in case the other side does not proactively respond.
–Aditya Kapur
In the “FIX_Transport_1 1.pdf”, under the section “Logon Message NextExpectedMsgSeqNum Processing” it is stated that “Neither side should generate a ResendRequest based on the MsgSeqNum (34) of the incoming Logon message but should expect any gaps to be filled automatically…”.
But at the same just above this section in the “Response by Message Type” table, for Logon message it is stated that “Must always be the first message transmitted. Authenticate and accept the connection. After sending the Logon confirmation back, send a ResendRequest if a message gap was detected in the Logon sequence number.”
As these two statements are contradictory, I am a bit confused about handling a Logon Request with a greater than expected sequence number.
In this case should:
a) A ResendRequest be sent to the counterparty or
b) An auto resynchronization should be expected from the client, after sending Logon Response with the NextExpectedMsgSeqNum (Tag 789)?Will there be any change in handling the sequence number (in Tag 34), received in the Logon message?
Thanks in Advance,
Vinay M