Re: [Quickfix-developers] Already sent ResendRequest ... Not sending another.

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

Well, the initiator sent a resend request from 197648 to 0 after logging 
in, and the acceptor responded with a sequence reset from 197648 to 
197651.  No messages would have been queued, so no queued messages would 
have been processed.  So yeah, I would think that it is not being reset 
in the correct place.

--oren

> The change I just made to generateResendRequest will ensure that the 
> .second member of the range is always initialized to a real sequence 
> number, so the code there is fine.  What worries me though is the log 
> Scott attached not showing a message like "Processed QUEUED message: 
> #".  That is where the Session code resets the resend range to (0, 
> 0).  So if the "Processing QUEUED message" never shows up in the log, 
> the range would still have been ( 197648, 0) so changing 
> SessionState::resendRequested wouldn't have fixed the bug.
>
> I think the simplest and most reliable change is the one I made to 
> Session.cpp where the resendRange is initialized with a range of real 
> sequence numbers, and it not "open-ended" at the top ( e.g. 0 or 9999999).
>
> I am still slightly concerned however that there is a code-path by 
> which ::nextQueued isn't being called before ::next.  This says to me 
> that the logic for resetting the resend range belongs elsewhere.
>
>
>
> -- 
> Caleb Epstein
> caleb dot epstein at gmail dot com