Re: [Quickfix-developers] SequenceReset bug?

[<or...@qu...>]

I'm not sure I see this as a bug in quickfix, but rather a bug in the
counterprty.  Let me make sure I understand what you are saying.

You receive message 508, but expect 507
508 is queued
you request all messages up to 507
you are now expecting 508
the queued 508 message, which is the expected number, is processed
you should now expect 509, since you have process 508 which was not part
of the resend request
They send you a new message with sequence number 508, completely
different from the previous message they tagged with 508. Eep!  That's
not allowed.

> -------- Original Message --------
> Subject: [Quickfix-developers] SequenceReset bug?
> From: Kbo Keplowsky <kbo...@gm...>
> Date: Sun, June 22, 2008 9:21 am
> To: qui...@li...
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> Hi all,
> I've come across an issue that looks like a bug to me - i.e. not in accordance 
> with the FIX protocol.
> My system (QuickFix initiator) logs in, only to find out that the sequence 
> number is too high (508 instead of 507).
> That's cool, so it queues the current message (#508) and sends a resend 
> request (0 to 507).
> The counterparty responds, sending a sequence reset from 507 to 508 (basically 
> saying there's nothing to send, and that 508 is the next sequence number, I 
> assume).
> Now here's the problem - my system is satisfied, sets the next expected number 
> to 508, and processes the queued message (#508, remember?). This, however, 
> advances the sequence number...
> On the next heartbeat, my system gets a heartbeat response, with a sequence 
> number of (did you guess?) 508... which is reasonable for the counterparty, 
> but too low for my system, and so it disconnects. This can go on forever.
> What should I do? I've read the FIX specs, and it explicitly say that the 
> NewSeqNum field in the SequenceReset message is the next number sent by the 
> counterparty, so I believe the bug is with QuickFix, talking into account the 
> seqnum of the queued message...
> Help, please...
> Thanks,
> Kbo
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers