[This message was posted by Mahesh Kumaraguru of <[email protected]> to the "4.0 Session" discussion forum at http://fixprotocol.org/discuss/12. You can reply to it on-line at http://fixprotocol.org/discuss/read/e713035a - PLEASE DO NOT REPLY BY MAIL.]
[Start Quote from FIXT.1.1 pdf spec Page 44/66 Section Testcases] Buyside-oriented (session initiator) Logon and session initiation test case 1B Condition/Stimulus e. Receive any message other than a Logon message. Expected Behavior 1. Log an error “first message not a logon” 2. (Optional) Send Reject message with RefMsgSeqNum referencing message’s MsgSeqNum with Text referencing error condition 3. Send Logout message with Text referencing error condition 4. Disconnect [End quote] I am quoting from the FIXT.1.1 spec because this scenario is not explained in FIX.4.0 specs and whenever there is a scenario not covered in an earlier FIX version, I refer to the latest / later versions to see if that scenario is covered and use that as my solution. > What actions are to be taken in general, if FIX engine receives an unexpected > message? > > If it is application message, it is obvious to forward to business logic, > provided logon has been completed. > > What about administrative message? For e.g. ResendRequest received when > waiting for Logon(Ack) etc? > > Should the sequence number be consumed? [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.
