Re: [Quickfix-developers] Problem with reset() because of generateLogout() if logon short before StartTime

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

Subert,

I believe this is a bug that was fixed in a later release.  Have you  
tried 1.12.4 with this scenario?  I believe that now when there is  
activity outside of the session time, the sequence numbers do not get  
incremented.

--oren

> We have a problem with QuickFix 1.11.2 (compared with 1.9.4 version
> where it was ok) as during reset() the generateLogout() is called too.
>
> If partner tries to connect/logon short before StartTime ( i.e.  
> outside
> the session times) then on our side
> 1) session is reseted
> 2) logout is sent (incrementing seq num)
> 3) session is reseted (reseting seq num)
> 4) session is reseted
>
> It seams that
> 1) the partner is suprised with our Logout and/or
> 2) by later connect/logon (after) StartTime the partner expects  
> SeqNum=2
> inside our next Logon message but we will send SeqNum=1 as we have
> reseted the session and the partner does not knows that (message too
> low).
>
> Questions:
> Is  Logout response (new in 1.11.2) allowed after Logon attempt short
> before StartTime (outside the session times), or would be better to  
> only
> disconnect (as in 1.9.4) ?
> Should generateLogout() be skipped (not sent) as consuming seqnum, if
> Logon is not accepted/responded and session is reseted because of
> checkSessionTimes ?
>
> Thank for help.