[QFJ-658] Sequence numbers not checked for incoming ResendRequest Created: 08/Dec/11  Updated: 02/Apr/15  Resolved: 16/Dec/13

Status: Closed
Project: QuickFIX/J
Component/s: Engine
Affects Version/s: 1.5.1
Fix Version/s: 1.6.0

Type: Bug Priority: Default
Reporter: Christoph John Assignee: Christoph John
Resolution: Duplicate Votes: 1
Labels: session

Issue Links:
Duplicate
duplicates QFJ-673 QFJ sequence problem following inboun... Closed

 Description   

When QF/J receives a ResendRequest it does not check for the MsgSeqNum of the ResendRequest. Depending on the MsgSeqNum on the ResendRequest it does the following (no PossDup flag was set):

  • MsgSeqNum on ResendRequest too low: QF/J performs the normal resending or SequenceReset, incoming sequence number is not altered
  • MsgSeqNum on ResendRequest correct: QF/J performs the normal resending or SequenceReset, incoming sequence number is incremented
  • MsgSeqNum on ResendRequest too high: QF/J performs the normal resending or SequenceReset, incoming sequence number is not altered

According to the spec (e.g. http://fixprotocol.org/documents/3070/FIX_Transport_1.1.pdf on pages 12 and 13) the behaviour should be as follows:

  • MsgSeqNum too low: terminate the connection
  • MsgSeqNum too high: perform the normal resending or SequenceReset, afterwards send a ResendRequest of your own to fill the gap

 Comments   
Comment by Christoph John [ 16/Dec/13 ]

Closing as duplicate since this is part of a bigger problem which is handled in QFJ-673.

Generated at Mon Apr 29 05:59:55 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.