Behaviour when Application Messages are sent with duplicate sequence numbers when PossDupFlag is not specified

, ,
1

Imported from previous forum

2

Hi,

Consider the following scenario:

  1. A client sends a Logon Message with MsgSeqNum =13
  2. The server identifies a Sequence Gap and sends a Resend Request.
  3. The client responds with a New Order message with MsgSeqNum=3 and 43(PossDupFlag)=Y
  4. Thereafter the client sends New order messagee with MsgSeqNum=4 and 43(PossDupFlag)=Y
  5. To fill the rest of the sequence gap (from 4 to 12), the client sends a Sequence Reset message.
  6. The client then submits another New order message with MsgSeqNum=12
  7. Thereafter the client sends an Order Amend Request with MsgSeqNum = 13.

In such a case, what is the expected response from the server when the amend request (or any application message) is sent with MsgSeqNum = 13?

Thanks,
Chavindri

3

Since server sent reset request on login with 34=13, at the time of amend, with 34=13 it doesn’t have a message with same msgsequence number. So as long as tag11 | 41 are correct, your amend should go through. However, there could be some other reason for a reject.