[This message was posted by John Prewett of Lava Trading <[EMAIL PROTECTED]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/b9f4a6f9 - PLEASE DO NOT REPLY BY MAIL.]
I have encountered this issue before. I believe: 1. A should ignore the out-of-sequence TestRequest as it is using the "thru infinity" method of handling sequence number gaps. The subsequent gap-fill it receives doesn't force it to take any action. 2. B should be aware that a response to the TestRequest won't be forthcoming because it received and responded to a ResendRequest which included the MsgSeqNum of the TestRequest message. So if B is waiting for a response to the gap-filled TestRequest, it is making a mistake. JohnP > Dear All, > > I have a question about correct processing of Test Request message (FIX > 4.4 version is used). > > Scenario is below: > > 1) Party A expects Logon with MsgSeqNum = 1. > 2) Party B sends Logon with MsgSeqNum = 57. > 3) Party B immediately sends Test Request with MsgSeqNum = 58. > 4) Party A sends confirming Logon. 5) Party A sends Resend Request with > BeginSeqNo = 1, EndSeqNo = 0 (what means infinity). > 5) Party B sends Sequence Reset with GapFill = Y and NewSeqNo = 59. > > Received Sequence Reset message shows that gap is filled, and Party A > should expect next message with MsgSeqNum = 59. > > But what is correct behaviour of Party A regarding Test Request with > MsgSeqNum = 58? It looks like it should be ignored because gap is > already filled. But what if Party B still waits for Heartbeat with > corresponding TestReqID? > > Could you please advise? > > Thank you in advance. [You can unsubscribe from this discussion group by sending a message to mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
