MsgSeqNum too low expecting 11 but received 4

MsgSeqNum too low expecting 11 but received 4

While working on FIX protocol to send and recieve message it’s very common to get exception and this is one which we get while trying to setup your environment.

quickfix.SessionException MsgSeqNum too low, expecting 11 but received 4

<20150815-15:00:42, FIX.4.2:FixClient8019->FixAcceptor, event> (Session FIX.4.2:FixClient8019->FixAcceptor schedule is daily, 00:00:00 UTC - 00:00:00 UTC (daily, 00:00:00 UTC - 00:00:00 UTC))
<20150815-15:00:42, FIX.4.2:FixClient8019->FixAcceptor, event> (Created session: FIX.4.2:FixClient8019->FixAcceptor)
Inside onCreate
Aug 15, 2015 11:00:42 AM quickfix.mina.NetworkingOptions logOption
INFO: Socket option: SocketTcpNoDelay=true
Aug 15, 2015 11:00:42 AM quickfix.mina.NetworkingOptions logOption
INFO: Socket option: SocketSynchronousWrites=false
Aug 15, 2015 11:00:42 AM quickfix.mina.NetworkingOptions logOption
INFO: Socket option: SocketSynchronousWriteTimeout=30000
Sending Order to Server
Aug 15, 2015 11:00:42 AM quickfix.mina.initiator.InitiatorIoHandler sessionCreated
INFO: MINA session created: /127.0.0.1:51377
<20150815-15:00:43, FIX.4.2:FixClient8019->FixAcceptor, outgoing> (8=FIX.4.2
9=80
35=A
34=10
49=FixClient8019
52=20150815-15:00:43.778
56=FixAcceptor
98=0
108=60
10=232
)
<20150815-15:00:43, FIX.4.2:FixClient8019->FixAcceptor, event> (Initiated logon request)
<20150815-15:00:43, FIX.4.2:FixClient8019->FixAcceptor, incoming> (8=FIX.4.2
9=79
35=A
34=1
49=FixAcceptor
52=20150815-15:00:43.858
56=FixClient8019
98=0
108=60
10=191
)
<20150815-15:00:43, FIX.4.2:FixClient8019->FixAcceptor, incoming> (8=FIX.4.2
9=76
35=2
34=2
49=FixAcceptor
52=20150815-15:00:43.858
56=FixClient8019
7=1
16=0
10=013
)
<20150815-15:00:43, FIX.4.2:FixClient8019->FixAcceptor, outgoing> (8=FIX.4.2
9=118
35=5
34=11
49=FixClient8019
52=20150815-15:00:43.889
56=FixAcceptor
58=MsgSeqNum too low, expecting 11 but received 1
10=189
)
<20150815-15:00:43, FIX.4.2:FixClient8019->FixAcceptor, event> (quickfix.SessionException MsgSeqNum too low, expecting 11 but received 1)
<20150815-15:00:43, FIX.4.2:FixClient8019->FixAcceptor, event> (Disconnecting)
Aug 15, 2015 11:00:44 AM quickfix.mina.initiator.InitiatorIoHandler sessionCreated
INFO: MINA session created: /127.0.0.1:49786
<20150815-15:00:45, FIX.4.2:FixClient8019->FixAcceptor, outgoing> (8=FIX.4.2
9=80
35=A
34=12
49=FixClient8019
52=20150815-15:00:45.767
56=FixAcceptor
98=0
108=60
10=234
)
<20150815-15:00:45, FIX.4.2:FixClient8019->FixAcceptor, event> (Initiated logon request)
<20150815-15:00:45, FIX.4.2:FixClient8019->FixAcceptor, incoming> (8=FIX.4.2
9=79
35=A
34=4
49=FixAcceptor
52=20150815-15:00:45.767
56=FixClient8019
98=0
108=60
10=195
)
<20150815-15:00:45, FIX.4.2:FixClient8019->FixAcceptor, outgoing> (8=FIX.4.2
9=118
35=5
34=13
49=FixClient8019
52=20150815-15:00:45.767
56=FixAcceptor
58=MsgSeqNum too low, expecting 11 but received 4
10=191
)
<20150815-15:00:45, FIX.4.2:FixClient8019->FixAcceptor, incoming> (8=FIX.4.2
9=76
35=2
34=5
49=FixAcceptor
52=20150815-15:00:45.767
56=FixClient8019
7=1
16=0
10=017
)
<20150815-15:00:45, FIX.4.2:FixClient8019->FixAcceptor, event> (quickfix.SessionException MsgSeqNum too low, expecting 11 but received 4)
<20150815-15:00:45, FIX.4.2:FixClient8019->FixAcceptor, event> (Disconnecting)
<20150815-15:00:45, FIX.4.2:FixClient8019->FixAcceptor, incoming> (8=FIX.4.2
9=67
35=5
34=6
49=FixAcceptor
52=20150815-15:00:45.767
56=FixClient8019
10=154
)
Stoping socketInitiator
Aug 15, 2015 11:00:45 AM quickfix.mina.SessionConnector logoutAllSessions
INFO: Logging out all sessions
Acknowledgement received: --> null

Solution: This exception happens if hou fix file format below is not mathcing with ther server files these file are:

and on Initiator side it should be somehting like below and file inside red box is not needed so delete them out:

Once you run your acceptor or server you will these extract will be generated by the API:

• This should fix the issue. (Probably after doing all these you may get same exception first time but second time onwareds it will work OK, this could be API level bug)
• For more informaiton please visit QuickFix site here