Resend Request simultanously by both ends

, ,
1

Imported from previous forum

2

[ original email was from Flavius Bindea - flav@flav.com ]
What should happen when both Acceptor and
Initiator send a Resend Request in the same time.

E.g.:
Acceptor detects that messages 15 to 20 are missing. It sends a Resend Request 15-0 with
MsgSeqNum=26.
Initiator detects that messages 17 to 24 are
missing. It sends a Resend Resquest 17-0 with
MsgSeqNum=22.
As is written in the specs (Ordered Message Processing) the acceptor should not process
message 21 and 22 before 15-20 (in this case
it should not process the Resend Request).
Same for the initiator : it should not process
message 26 (Resend Request), before 17-25.

Should we process administrative messages
during the gap fill process ?

3

Within the "Message Recovery" section of the FIX spec which describes the session-level implementation, there is a matrix of "Response by Message Type" with "Action to Be Taken on Sequence # mismatch". For Resend Request, it states "Perfrm the Resend processing first, followed by a ResendRequest of your own in order to fill the incoming message gap."

> What should happen when both Acceptor and
> Initiator send a Resend Request in the same time.
>
> E.g.:
> Acceptor detects that messages 15 to 20 are missing. It sends a Resend Request 15-0 with
> MsgSeqNum=26.
> Initiator detects that messages 17 to 24 are
> missing. It sends a Resend Resquest 17-0 with
> MsgSeqNum=22.
> As is written in the specs (Ordered Message Processing) the acceptor should not process
> message 21 and 22 before 15-20 (in this case
> it should not process the Resend Request).
> Same for the initiator : it should not process
> message 26 (Resend Request), before 17-25.
>
> Should we process administrative messages
> during the gap fill process ?
>
>
>