RE: [Quickfix-developers] Session Resetting

[Steinberg, J. <Jon...@bo...>]

Regarding your comment about the dropping connection being wrong- 

I was also suspicious of this. After a logout caused by a incorrect seq
num, shouldn't the counter party then accept a logon with the correct
seq num?

 

Thanks again for your help

 

 

Jonathan Steinberg

 

________________________________

From: qui...@li...
[mailto:qui...@li...] On Behalf Of
John Hensley
Sent: Tuesday, February 28, 2006 7:24 AM
To: qui...@li...
Subject: RE: [Quickfix-developers] Session Resetting

 

Right, but things are OK from there until just before noon. Then for
some reason Jonathan's engine is logging out, and it looks like the
counterparty is not acknowledging the logout message and resetting
sequence numbers. From the socket error logged after the "Disconnecting"
message, they're just dropping the connection. I think that's wrong, but
the more pressing question is Jonathan's: why's QuickFIX disconnecting
and resetting in the first place?

 

________________________________

From: Caleb Epstein [mailto:cal...@gm...] 
Sent: Monday, February 27, 2006 11:49 PM
To: Steinberg, Jonathan
Cc: John Hensley; qui...@li...
Subject: Re: [Quickfix-developers] Session Resetting

On 2/27/06, Steinberg, Jonathan <Jon...@bo...>
wrote: 

	There was also a sequence reset at 5:00, but nothing since that
point - here is the complete event log with the sequence reset put back
.

	Where else would I look?

	What events would cause a logout/session reset?


Hitting the Session's configured StartTime.  From an earlier mail, you
have:

[DEFAULT] 

HeartBtInt=60

StartTime=10:00:00

EndTime=01:00:00


 Which would agree with an 05:00 local time reset of sequence numbers
(StartTime is in GMT).

-- 
Caleb Epstein
caleb dot epstein at gmail dot com