Re: [Quickfixj-users] Unexpected "MsgSeqNum too low, expecting X but received Y"

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Here is the message log for 2.1.1.

2021-03-26 08:42:35.704  INFO 40318 --- [nio-9051-exec-2]
c.m.f.s.listener.FixApplicationListener  : =>> Send toApp message to FIX
gateway, MsgType=ExecutionReport(8), MsgSeqNum=55
sessionId=FIXT.1.1:Initiator->Acceptor
message=8=FIXT.1.1^9=338^35=8^34=55^49=Initiator^52=20210326-08:42:35.703^56=Acceptor^1=108331^14=0^15=USD^17=1115569_1615646513221_927^22=971^37=1115569^38=1^39=0^40=4^44=290.2^48=BCH/USD^54=1^55=BCHUSD^59=1^60=20210313-14:41:53.099^150=0^151=1^167=CRYPTSPOT^423=3^460=15^581=1^965=1^1084=4^1138=0^453=2^448=MATX^447=G^452=22^448=MEHSAG1601PIND90805^447=D^452=3^10=103^
2021-03-26 08:42:35.704  INFO 40318 --- [nio-9051-exec-2]
c.m.f.s.listener.SenderMessageCracker    : ExecutionReport - handle
ExecutionReport message
2021-03-26 08:42:35.707  INFO 40318 --- [nio-9051-exec-2]
c.m.f.s.d.handle.MessageHandlerContext   : ===cracker type :TO_APP_REJECT
2021-03-26 08:42:35.707  INFO 40318 --- [nio-9051-exec-2]
c.m.f.s.d.handle.MessageHandlerContext   : ====do handle
2021-03-26 08:42:35.707  INFO 40318 --- [nio-9051-exec-2]
c.m.f.s.d.h.ToAppRejectMessageHandler    : ===not approved retransmit
2021-03-26 08:42:35.708  INFO 40318 --- [nio-9051-exec-2]
c.m.f.s.listener.FixApplicationListener  : added
possDupFlag:8=FIXT.1.1^9=343^35=8^34=55^43=N^49=Initiator^52=20210326-08:42:35.703^56=Acceptor^1=108331^14=0^15=USD^17=1115569_1615646513221_927^22=971^37=1115569^38=1^39=0^40=4^44=290.2^48=BCH/USD^54=1^55=BCHUSD^59=1^60=20210313-14:41:53.099^150=0^151=1^167=CRYPTSPOT^423=3^460=15^581=1^965=1^1084=4^1138=0^453=2^448=MATX^447=G^452=22^448=MEHSAG1601PIND90805^447=D^452=3^10=086^
2021-03-26 08:42:35.708  INFO 40318 --- [nio-9051-exec-2]
c.m.f.s.listener.FixApplicationListener  : possDubFlag:false
2021-03-26 08:42:35.711  INFO 40318 --- [nio-9051-exec-2]
c.m.f.s.infra.SenderApplicationService   : [API Call]
sendHigherSeqNoThanExcepted success，higherThanExpected=55, msgType=8
2021-03-26 08:42:35.714  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.FixApplicationListener  : <<= Initiator received fromAdmin
message, MsgType=Resend(2), MsgSeqNum=42
sessionId: FIXT.1.1:Initiator->Acceptor
message:
8=FIXT.1.1^9=78^35=2^34=42^49=Acceptor^52=20210326-08:42:35.711^56=Initiator^369=49^7=50^16=0^10=063^
2021-03-26 08:42:35.714  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.SenderMessageCracker    : ResendRequest - from,
beginSeqNo=50, endSeqNo=0
2021-03-26 08:42:35.718  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.FixApplicationListener  : =>> Send toApp message to FIX
gateway, MsgType=ExecutionReport(8), MsgSeqNum=55
sessionId=FIXT.1.1:Initiator->Acceptor
message=8=FIXT.1.1^9=369^35=8^34=55^43=Y^49=Initiator^52=20210326-08:42:35.718^56=Acceptor^122=20210326-08:42:35.703^1=108331^14=0^15=USD^17=1115569_1615646513221_927^22=971^37=1115569^38=1^39=0^40=4^44=290.2^48=BCH/USD^54=1^55=BCHUSD^59=1^60=20210313-14:41:53.099^150=0^151=1^167=CRYPTSPOT^423=3^460=15^581=1^965=1^1084=4^1138=0^453=2^448=MATX^447=G^452=22^448=MEHSAG1601PIND90805^447=D^452=3^10=113^
2021-03-26 08:42:35.718  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.SenderMessageCracker    : ExecutionReport - handle
ExecutionReport message
2021-03-26 08:42:35.718  INFO 40318 --- [ssage Processor]
c.m.f.s.d.handle.MessageHandlerContext   : ===cracker type :TO_APP_REJECT
2021-03-26 08:42:35.718  INFO 40318 --- [ssage Processor]
c.m.f.s.d.handle.MessageHandlerContext   : ====do handle
2021-03-26 08:42:35.718  INFO 40318 --- [ssage Processor]
c.m.f.s.d.h.ToAppRejectMessageHandler    : ===not approved retransmit
2021-03-26 08:42:35.718  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.FixApplicationListener  : added
possDupFlag:8=FIXT.1.1^9=369^35=8^34=55^43=N^49=Initiator^52=20210326-08:42:35.718^56=Acceptor^122=20210326-08:42:35.703^1=108331^14=0^15=USD^17=1115569_1615646513221_927^22=971^37=1115569^38=1^39=0^40=4^44=290.2^48=BCH/USD^54=1^55=BCHUSD^59=1^60=20210313-14:41:53.099^150=0^151=1^167=CRYPTSPOT^423=3^460=15^581=1^965=1^1084=4^1138=0^453=2^448=MATX^447=G^452=22^448=MEHSAG1601PIND90805^447=D^452=3^10=102^
2021-03-26 08:42:35.718  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.FixApplicationListener  : possDubFlag:false
2021-03-26 08:42:35.719  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.FixApplicationListener  : =>> Send toAdmin message to FIX
gateway, MsgType=SequenceReset(4), MsgSeqNum=50
sessionId: FIXT.1.1:Initiator->Acceptor
message:
8=FIXT.1.1^9=104^35=4^34=50^43=Y^49=Initiator^52=20210326-08:42:35.719^56=Acceptor^122=20210326-08:42:35.718^36=55^123=Y^10=182^
2021-03-26 08:42:35.719  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.SenderMessageCracker    : SequenceReset - to
2021-03-26 08:42:35.719  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.SenderMessageCracker    : expected sender num compare to
new seq no:true,NewSeqNo:55,ExpectedSenderNum:56
2021-03-26 08:42:35.719  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.SenderMessageCracker    : SequenceReset
finally:8=FIXT.1.1^9=104^35=4^34=50^43=Y^49=Initiator^52=20210326-08:42:35.719^56=Acceptor^122=20210326-08:42:35.718^36=55^123=Y^10=182^
2021-03-26 08:42:35.726  INFO 40318 --- [ssage Processor]
c.m.f.s.listener.FixApplicationListener  : <<= Initiator received fromAdmin
message, MsgType=Logout(5), MsgSeqNum=43
sessionId: FIXT.1.1:Initiator->Acceptor
message:
8=FIXT.1.1^9=126^35=5^34=43^49=Acceptor^52=20210326-08:42:35.723^56=Initiator^369=55^1128=9^58=MsgSeqNum
too low, expecting 56 but received 55^10=010^

Thanks
Best regards.

Christoph John <chr...@ma...> 于2021年3月26日周五 下午2:43写道：

> Just saw that you are using 2.1.1. The other side uses the same version?
> Could you maybe try to reproduce with version 2.2.0 and paste the relevant
> message log? Or at least paste the message log from your currently used
> version.
> Thanks
>
> Am 26. März 2021 07:40:23 MEZ schrieb Christoph John <
> chr...@ma...>:
>>
>> Hi,
>> which version of QFJ are you and the other side using?
>> Could you please directly paste the relevant message log from your side
>> and if possible also from the acceptor?
>> Thanks,
>> Chris.
>
>