Actions on unexpected message?

, ,
1

Imported from previous forum

2

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?

3

[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?