Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Q quickfix
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 48
    • Issues 48
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • quickfixgo
  • quickfix
  • Issues
  • #406
Closed
Open
Issue created Jun 08, 2020 by Administrator@rootContributor

FileStore for initiator resetting sequence number

Created by: lkcole

I am using FileStoreFactory for managing 1 session where the ResetOn* configuration settings are unset (they all default to N).

Upon receiving a message from the acceptor to set my sequence number, I stopped the application. After I was sure the process was down, I modified the senderseqnums file associated with the session to the one specified by the acceptor and save. I verified the file was correct and of the appropriate permissions (640). Upon restarting the application, the sequence number populated by the engine was 1 AGAIN. The senderseqnums reflects the same thing.

I've walked through the FileStore.go logic as well as the session.go logic and can't figure out why it would reset. And if it does reset, there should be an event generated.

This appears to be a bug or something glaringly obvious that I'm missing. The pertinent log is below. Any help in resolving this issue would be greatly appreciated.

<2020-06-08 22:41:11.505777213 +0000 UTC, FIX.4.2:XXXXXX/TRADE_CAPTURE/US,CA->CME/68, event>
(Created session)
<2020-06-08 22:41:11.506123792 +0000 UTC, FIX.4.2:XXXXXX/TRADE_CAPTURE/US,CA, event>
(Connecting to: aaa.zzz.yyy.xxx:123456)
<2020-06-08 22:41:11.507635196 +0000 UTC, FIX.4.2:XXXXXX/TRADE_CAPTURE/US,CA->CME/68, event>
(Sending logon request)
MsgSeqNum:  1
2020/06/08 22:41:11 Attempting login with session:  FIX.4.2:XXXXXX/TRADE_CAPTURE/US,CA->CME/68
<2020-06-08 22:41:11.509113112 +0000 UTC, FIX.4.2:XXXXXX/TRADE_CAPTURE/US,CA->CME/68, outgoing>
 (8=FIX.4.29=25935=A34=149=XXXXXX50=TRADE_CAPTURE52=20200608-22:41:11.50756=CME57=68142=US,CA369=0108=30141=N354=20355=Rw9D0zl1pWcKprxUo9tL1400=CME-1-SHA-2561401=431402=f_MugoSdJ-LzAtbUfp4-7bJ42V-m3dFma7G4vjCL52M1603=CME Trade Capture1604=0.11605=Company10=071)
<2020-06-08 22:41:11.512042318 +0000 UTC, FIX.4.2:XXXXXX/TRADE_CAPTURE/US,CA->CME/68, incoming>
(8=FIX.4.29=19635=534=2158369=92052=20200608-22:41:11.51049=CME50=6856=XXXXXX57=TRADE_CAPTURE143=US,CA58=Sequence number received lower than expected. Expected [921] Received 1. Logout forced.789=92110=229)
cme-trade-capture_1  | 2020/06/08 22:41:11 Logged out:  FIX.4.2:XXXXXX/TRADE_CAPTURE/US,CA->CME/68
Assignee
Assign to
Time tracking