[Quickfix-developers] SequenceReset bug?

[Kbo K. <kbo...@gm...>]

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