{{Quickfixn}} Incoming sequence number lower than expected.

[olamide olatunji]

Hi Jeff,
Looks like your engine reset sequence number when you restarted and your
counterparty didn't.

You'll have to talk to your counterparty to reset sequence.

You should also check their spec for info regarding session resets, so you
can configure your engine properly.

Best regards,

Olamide

On Tue, Sep 22, 2015 at 8:31 AM, Jeff S. <jeff at alphafinhk.com> wrote:

>
>
> Hello,
>
>
>
> My broker tells me that tag 141 is not supported and should be set to
> “N”.  Once I did this,
>
> I started receiving incoming sequence numbers lower than expected which
> resulted in
>
> disconnects.
>
>
>
> How do I reset the expected incoming sequence number or tell the
> counterparty to reset
>
> their outgoing seq number?  …or is there something else I should be doing?
>
>
>
> Thanks very  much,
>
> Jeff
>
>
>
> Message sequence:
>
>
>
> <incoming>
> 8=FIX.4.2_9=000071_35=A_34=000046_43=N_52=20150922-05:21:36_49=IB_56=direc513_98=0_108=30_10=011_
>
> <outgoing>
> 8=FIX.4.2_9=107_35=5_34=275_49=direc513_52=20150922-05:21:35.443_56=IB_58=MsgSeqNum
> too low, expecting 252 but received 46_10=214_
>
> A first chance exception of type 'QuickFix.QuickFIXException' occurred in
> QuickFix.dll
>
> <event> Verify failed: MsgSeqNum too low, expecting 252 but received 46
>
> <event> Session FIX.4.2:direc513->IB disconnecting: Verify failed:
> MsgSeqNum too low, expecting 252 but received 46
>
> The thread 0x87c has exited with code 0 (0x0).
>
>
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20150922/ada67e51/attachment-0002.htm>