Re: [Quickfix-developers] ResendRequest/SequenceReset-GapFill results in losing important messages

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

Do you have logs?

--oren

On Nov 9, 2006, at 2:25 PM, Alex Shterenberg wrote:

> Hi
>
>
>
> Quickfix seems to ignore an important message in what looks like a =20
> race condition.
>
> Consider this scenario:
>
>
>
> Quickfix sends a login, seq# 3319
>
> OtherEngine responds to login with seq#3323
>
> Quickfix missed #3322 when it previously disconnected, so it sends =20
> a ResendRequest for #3322, which happens to be a heartbeat
>
> before OtherEngine receives the resend request, it sends out the =20
> Trading Session Status, #3324
>
> OtherEngine sends a Gap-Fill resetting the sequence number to #3325
>
> Session continues with OtherEngine=92s sequence number at 3325 and =20
> Quickfix=92s sequence number at 3321
>
>
>
> My app never hears about the trading session status message.
>
>
>
> If this is not a problem with quickfix, what can I do to ensure =20
> that I never miss the trading status message?
>
>
>
> Thanks!
>
>
>
> Alex