Thread: RE: [Quickfix-developers] Session Resetting
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-developers
|
From: John H. <jhe...@bo...> - 2006-02-27 21:10:49
|
Looks like your sequence numbers are out of sync; your counterparty thinks your conversation is up to 425, and you're at 1. You need to have them reset, or somehow get your outgoing sequence number caught up. I have a Java utility I use with QF/J; I don't know whether there's something similar for 1.11.0. =20 BTW, I'd obscure the sender and target comp IDs too. Maybe I'm just paranoid. =20 John ________________________________ From: qui...@li... [mailto:qui...@li...] On Behalf Of Steinberg, Jonathan Sent: Monday, February 27, 2006 3:34 PM To: qui...@li... Subject: [Quickfix-developers] Session Resetting I am having a tough time with a session resetting itself=20 I am using Quickfix 1.11.0, quickifx_net wrappers with c#, VS2003. =20 Here is my config=20 =20 [DEFAULT] HeartBtInt=3D60 StartTime=3D10:00:00 EndTime=3D01:00:00 =20 [SESSION] ConnectionType=3Dinitiator SocketConnectHost=3Dxxx.xx.xxx.xxx=20 SocketConnectPort=3D17988 BeginString=3DFIX.4.0 TargetCompID=3DBOFA SenderCompID=3DBFPG ValidateFieldsOutOfOrder=3DN CheckLatency=3DN UseDataDictionary=3DN SessionQualifier=3DCASHDESK =20 =20 Here is the event log: =20 2006-02-24 05:00:36.587 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 05:00:36.650 Connection succeeded 2006-02-24 05:00:37.757 Initiated logon request 2006-02-24 05:00:37.837 Received logon response 2006-02-24 11:57:45.263 Disconnecting 2006-02-24 11:57:45.653 Socket Error 2006-02-24 11:58:07.747 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:58:07.763 Connection succeeded 2006-02-24 11:58:08.777 Initiated logon request 2006-02-24 11:58:08.980 Received logout request 2006-02-24 11:58:09.027 Sending logout response 2006-02-24 11:58:09.027 Disconnecting 2006-02-24 11:58:09.027 Socket Error 2006-02-24 11:58:37.760 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:58:38.760 Connection failed 2006-02-24 11:59:07.773 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:59:08.727 Connection failed =20 =20 Here are the incoming and outgoing logs: heartbeat out 2006-02-24 11:56:37.037 8=3DFIX.4.09=3D4935=3D034=3D42249=3DBFPG52=3D20060224-16:56:3756=3DBOFA10= =3D177 heartbeat in 2006-02-24 11:56:47.127 8=3DFIX.4.09=3D5435=3D049=3DBOFA56=3DBFPG34=3D41943=3DN52=3D20060224-16:5= 6:4710=3D167 heartbeat out 2006-02-24 11:57:37.170 8=3DFIX.4.09=3D4935=3D034=3D42349=3DBFPG52=3D20060224-16:57:3756=3DBOFA10= =3D179 logout out 2006-02-24 11:57:45.187 8=3DFIX.4.09=3D4935=3D534=3D42449=3DBFPG52=3D20060224-16:57:4556=3DBOFA10= =3D184 login out 2006-02-24 11:58:08.763 8=3DFIX.4.09=3D5935=3DA34=3D149=3DBFPG52=3D20060224-16:58:0856=3DBOFA98=3D= 0108=3D6010=3D120 logout in 2006-02-24 11:58:08.967 8=3DFIX.4.09=3D17835=3D549=3DBOFA56=3DBFPG34=3D42043=3DN52=3D20060224-16:= 58:0958=3DCatastr opic Error:=20 Incoming sequence number (1) is less than expected (425) without PossDupFlag being set. Logging=20 out.10=3D163 logout out 2006-02-24 11:58:09.013 8=3DFIX.4.09=3D4735=3D534=3D249=3DBFPG52=3D20060224-16:58:0856=3DBOFA10=3D= 078 =20 =20 I cannot figure out for the life of me why this session disconnected. =20 Additionally, the other system becomes unavailbable when this happens, and I see the outgoing messages on the follwing Monday (2/27) are logout messages again: 2006-02-27 05:00:26.943 8=3DFIX.4.09=3D4735=3D534=3D149=3DBFPG52=3D20060227-10:00:2656=3DBOFA10=3D= 061 which repeats until the other system resets itself. =20 How can I investigate the reason for the session reset?=20 Thanks for any help =20 =20 Jonathan Steinberg =20 =20 =20 =20 |
|
From: John H. <jhe...@bo...> - 2006-02-27 21:27:10
|
I hate it when you see what you should have read before you hit send, a minute after you hit send. Is there really nothing in your logs between the receipt of the logon response at 05:00 and that first disconnect, where your sequence numbers got reset? ________________________________ From: qui...@li... [mailto:qui...@li...] On Behalf Of John Hensley Sent: Monday, February 27, 2006 4:10 PM To: Steinberg, Jonathan; qui...@li... Subject: RE: [Quickfix-developers] Session Resetting Looks like your sequence numbers are out of sync; your counterparty thinks your conversation is up to 425, and you're at 1. You need to have them reset, or somehow get your outgoing sequence number caught up. I have a Java utility I use with QF/J; I don't know whether there's something similar for 1.11.0. =20 BTW, I'd obscure the sender and target comp IDs too. Maybe I'm just paranoid. =20 John ________________________________ From: qui...@li... [mailto:qui...@li...] On Behalf Of Steinberg, Jonathan Sent: Monday, February 27, 2006 3:34 PM To: qui...@li... Subject: [Quickfix-developers] Session Resetting I am having a tough time with a session resetting itself=20 I am using Quickfix 1.11.0, quickifx_net wrappers with c#, VS2003. =20 Here is my config=20 =20 [...] =20 Here is the event log: =20 2006-02-24 05:00:36.587 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 05:00:36.650 Connection succeeded 2006-02-24 05:00:37.757 Initiated logon request 2006-02-24 05:00:37.837 Received logon response 2006-02-24 11:57:45.263 Disconnecting 2006-02-24 11:57:45.653 Socket Error 2006-02-24 11:58:07.747 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:58:07.763 Connection succeeded 2006-02-24 11:58:08.777 Initiated logon request 2006-02-24 11:58:08.980 Received logout request 2006-02-24 11:58:09.027 Sending logout response 2006-02-24 11:58:09.027 Disconnecting 2006-02-24 11:58:09.027 Socket Error 2006-02-24 11:58:37.760 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:58:38.760 Connection failed 2006-02-24 11:59:07.773 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:59:08.727 Connection failed =20 =20 Here are the incoming and outgoing logs: heartbeat out 2006-02-24 11:56:37.037 8=3DFIX.4.09=3D4935=3D034=3D42249=3DBFPG52=3D20060224-16:56:3756=3DBOFA10= =3D177 heartbeat in 2006-02-24 11:56:47.127 8=3DFIX.4.09=3D5435=3D049=3DBOFA56=3DBFPG34=3D41943=3DN52=3D20060224-16:5= 6:4710=3D167 heartbeat out 2006-02-24 11:57:37.170 8=3DFIX.4.09=3D4935=3D034=3D42349=3DBFPG52=3D20060224-16:57:3756=3DBOFA10= =3D179 logout out 2006-02-24 11:57:45.187 8=3DFIX.4.09=3D4935=3D534=3D42449=3DBFPG52=3D20060224-16:57:4556=3DBOFA10= =3D184 login out 2006-02-24 11:58:08.763 8=3DFIX.4.09=3D5935=3DA34=3D149=3DBFPG52=3D20060224-16:58:0856=3DBOFA98=3D= 0108=3D6010=3D120 logout in 2006-02-24 11:58:08.967 8=3DFIX.4.09=3D17835=3D549=3DBOFA56=3DBFPG34=3D42043=3DN52=3D20060224-16:= 58:0958=3DCatastr opic Error:=20 Incoming sequence number (1) is less than expected (425) without PossDupFlag being set. Logging=20 out.10=3D163 logout out 2006-02-24 11:58:09.013 8=3DFIX.4.09=3D4735=3D534=3D249=3DBFPG52=3D20060224-16:58:0856=3DBOFA10=3D= 078 =20 =20 I cannot figure out for the life of me why this session disconnected. =20 Additionally, the other system becomes unavailbable when this happens, and I see the outgoing messages on the follwing Monday (2/27) are logout messages again: 2006-02-27 05:00:26.943 8=3DFIX.4.09=3D4735=3D534=3D149=3DBFPG52=3D20060227-10:00:2656=3DBOFA10=3D= 061 which repeats until the other system resets itself. =20 How can I investigate the reason for the session reset?=20 Thanks for any help =20 =20 Jonathan Steinberg =20 =20 =20 =20 |
|
From: Steinberg, J. <Jon...@bo...> - 2006-02-28 00:07:57
|
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 . 2006-02-24 05:00:36.587 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 05:00:36.650 Connection succeeded 2006-02-24 05:00:37.757 Initiated logon request 2006-02-24 05:00:37.837 Received logon response 2006-02-24 05:00:37.867 MsgSeqNum too high, expecting 2 but received 4 2006-02-24 05:00:37.993 Sent ResendRequest FROM: 2 TO: 999999 2006-02-24 05:00:38.210 Received SequenceReset FROM: 2 TO: 5 2006-02-24 05:01:38.190 ResendRequest for messages FROM: 2 TO: 3 has been satisfied. 2006-02-24 11:57:45.263 Disconnecting 2006-02-24 11:57:45.653 Socket Error 2006-02-24 11:58:07.747 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:58:07.763 Connection succeeded 2006-02-24 11:58:08.777 Initiated logon request 2006-02-24 11:58:08.980 Received logout request 2006-02-24 11:58:09.027 Sending logout response 2006-02-24 11:58:09.027 Disconnecting 2006-02-24 11:58:09.027 Socket Error 2006-02-24 11:58:37.760 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:58:38.760 Connection failed 2006-02-24 11:59:07.773 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:59:08.727 Connection failed Where else would I look? What events would cause a logout/session reset? Jonathan Steinberg ________________________________ From: John Hensley [mailto:jhe...@bo...] Sent: Monday, February 27, 2006 4:27 PM To: Steinberg, Jonathan; qui...@li... Subject: RE: [Quickfix-developers] Session Resetting I hate it when you see what you should have read before you hit send, a minute after you hit send. Is there really nothing in your logs between the receipt of the logon response at 05:00 and that first disconnect, where your sequence numbers got reset? ________________________________ From: qui...@li... [mailto:qui...@li...] On Behalf Of John Hensley Sent: Monday, February 27, 2006 4:10 PM To: Steinberg, Jonathan; qui...@li... Subject: RE: [Quickfix-developers] Session Resetting Looks like your sequence numbers are out of sync; your counterparty thinks your conversation is up to 425, and you're at 1. You need to have them reset, or somehow get your outgoing sequence number caught up. I have a Java utility I use with QF/J; I don't know whether there's something similar for 1.11.0. BTW, I'd obscure the sender and target comp IDs too. Maybe I'm just paranoid. John ________________________________ From: qui...@li... [mailto:qui...@li...] On Behalf Of Steinberg, Jonathan Sent: Monday, February 27, 2006 3:34 PM To: qui...@li... Subject: [Quickfix-developers] Session Resetting I am having a tough time with a session resetting itself I am using Quickfix 1.11.0, quickifx_net wrappers with c#, VS2003. Here is my config [...] Here is the event log: 2006-02-24 05:00:36.587 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 05:00:36.650 Connection succeeded 2006-02-24 05:00:37.757 Initiated logon request 2006-02-24 05:00:37.837 Received logon response 2006-02-24 11:57:45.263 Disconnecting 2006-02-24 11:57:45.653 Socket Error 2006-02-24 11:58:07.747 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:58:07.763 Connection succeeded 2006-02-24 11:58:08.777 Initiated logon request 2006-02-24 11:58:08.980 Received logout request 2006-02-24 11:58:09.027 Sending logout response 2006-02-24 11:58:09.027 Disconnecting 2006-02-24 11:58:09.027 Socket Error 2006-02-24 11:58:37.760 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:58:38.760 Connection failed 2006-02-24 11:59:07.773 Connecting to xxx.xx.xx.xxx on port 17988 2006-02-24 11:59:08.727 Connection failed Here are the incoming and outgoing logs: heartbeat out 2006-02-24 11:56:37.037 8=FIX.4.09=4935=034=42249=BFPG52=20060224-16:56:3756=BOFA10=177 heartbeat in 2006-02-24 11:56:47.127 8=FIX.4.09=5435=049=BOFA56=BFPG34=41943=N52=20060224-16:56:4710=167 heartbeat out 2006-02-24 11:57:37.170 8=FIX.4.09=4935=034=42349=BFPG52=20060224-16:57:3756=BOFA10=179 logout out 2006-02-24 11:57:45.187 8=FIX.4.09=4935=534=42449=BFPG52=20060224-16:57:4556=BOFA10=184 login out 2006-02-24 11:58:08.763 8=FIX.4.09=5935=A34=149=BFPG52=20060224-16:58:0856=BOFA98=0108=6010=120 logout in 2006-02-24 11:58:08.967 8=FIX.4.09=17835=549=BOFA56=BFPG34=42043=N52=20060224-16:58:0958=Catastr opic Error: Incoming sequence number (1) is less than expected (425) without PossDupFlag being set. Logging out.10=163 logout out 2006-02-24 11:58:09.013 8=FIX.4.09=4735=534=249=BFPG52=20060224-16:58:0856=BOFA10=078 I cannot figure out for the life of me why this session disconnected. Additionally, the other system becomes unavailbable when this happens, and I see the outgoing messages on the follwing Monday (2/27) are logout messages again: 2006-02-27 05:00:26.943 8=FIX.4.09=4735=534=149=BFPG52=20060227-10:00:2656=BOFA10=061 which repeats until the other system resets itself. How can I investigate the reason for the session reset? Thanks for any help Jonathan Steinberg |
|
From: Caleb E. <cal...@gm...> - 2006-02-28 04:48:53
|
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=3D60 > > StartTime=3D10:00:00 > > EndTime=3D01: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 |
|
From: John H. <jhe...@bo...> - 2006-02-28 12:23:56
|
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? =20 ________________________________ From: Caleb Epstein [mailto:cal...@gm...]=20 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:=20 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]=20 HeartBtInt=3D60 StartTime=3D10:00:00 EndTime=3D01:00:00 Which would agree with an 05:00 local time reset of sequence numbers (StartTime is in GMT). --=20 Caleb Epstein caleb dot epstein at gmail dot com=20 |
|
From: Steinberg, J. <Jon...@bo...> - 2006-02-28 16:35:03
|
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 |
|
From: Dale W. <wil...@oc...> - 2006-02-28 17:13:54
|
Hi Jonathan and John,
Steinberg, Jonathan wrote:
> 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?
>
Not according to the standard. The FIX 4.2 standard says:
If the incoming message has a sequence number less than expected and the
PossDupFlag is not set, it indicates a serious error. It is strongly
recommended that the session
be terminated and manual intervention be initiated.
Of course if the initiator then reconnects and sends a valid login it
should work.
Dale
>
>
> 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...
> <mailto: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
>
--
-----------------------------------------------------
Dale Wilson, Senior Software Engineer
Object Computing, Inc. (OCI)
http://www.ociweb.com/ http://www.theaceorb.com/
----------------------------------------------------
|
|
From: Oren M. <or...@qu...> - 2006-02-28 17:56:54
|
How often does this happen Jonathan. Is it repeatable? Does it happen everyday? --oren Steinberg, Jonathan wrote: > 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... > <mailto: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 > |
|
From: John H. <jhe...@bo...> - 2006-02-28 16:46:31
|
I believe if you had sent the logon with the sequence number they were expecting, it should have worked. That could be your workaround, if you can figure out how to adjust your sequence numbers, but the real problem is your engine deciding it needed to reset. =20 Oren? Any idea what could cause this? ________________________________ From: Steinberg, Jonathan [mailto:Jon...@bo...] Sent: Tuesday, February 28, 2006 11:35 AM To: John Hensley; qui...@li... Subject: RE: [Quickfix-developers] Session Resetting Regarding your comment about the dropping connection being wrong-=20 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? =20 Thanks again for your help =20 =20 Jonathan Steinberg =20 ________________________________ 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 =20 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? =20 ________________________________ From: Caleb Epstein [mailto:cal...@gm...]=20 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:=20 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]=20 HeartBtInt=3D60 StartTime=3D10:00:00 EndTime=3D01:00:00 Which would agree with an 05:00 local time reset of sequence numbers (StartTime is in GMT). --=20 Caleb Epstein caleb dot epstein at gmail dot com=20 |
|
From: Steinberg, J. <Jon...@bo...> - 2006-03-01 00:40:54
|
It happens sporadically. I can't reproduce it at will. It happened on 2/24/06 at 11:58 am for both of the sessions I have set up, and again today (2/28) at 9:43 am for one session, and at 2:30 Pm for another session It could certainly have been some problem in my application, but I can't find out what it is. I am really looking for ideas as to where to look; It would be helpful to know what else would cause a logout/reset to happen, other than the session times defined in the config file. Thanks again Jonathan Steinberg -----Original Message----- From: Oren Miller [mailto:or...@qu...] Sent: Tuesday, February 28, 2006 12:57 PM To: Steinberg, Jonathan Cc: John Hensley; qui...@li... Subject: Re: [Quickfix-developers] Session Resetting How often does this happen Jonathan. Is it repeatable? Does it happen everyday? --oren Steinberg, Jonathan wrote: > 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... > <mailto: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 > |
|
From: Oren M. <or...@qu...> - 2006-03-01 00:44:49
|
Well it can happen if the counterparty requests a sequence reset on logon. Doesn't seem to be the likely cause in this case. It happens when the session time expires as you know. There is also a reset method and methods to set the sequence numbers which can be called by anyone. I'll investigate the code to see if there is some other possibility. Hopefully your logs can be used to create a test case which might expose something. --oren Steinberg, Jonathan wrote: >It happens sporadically. I can't reproduce it at will. > >It happened on 2/24/06 at 11:58 am for both of the sessions I have set >up, and again today (2/28) at 9:43 am for one session, and at 2:30 Pm >for another session >It could certainly have been some problem in my application, but I can't >find out what it is. I am really looking for ideas as to where to look; >It would be helpful to know what else would cause a logout/reset to >happen, other than the session times defined in the config file. > >Thanks again > >Jonathan Steinberg > > >-----Original Message----- >From: Oren Miller [mailto:or...@qu...] >Sent: Tuesday, February 28, 2006 12:57 PM >To: Steinberg, Jonathan >Cc: John Hensley; qui...@li... >Subject: Re: [Quickfix-developers] Session Resetting > >How often does this happen Jonathan. Is it repeatable? Does it happen >everyday? > >--oren > >Steinberg, Jonathan wrote: > > > >>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... >><mailto: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 >> >> >> > > > > |
|
From: Steinberg, J. <Jon...@bo...> - 2006-03-01 20:05:57
|
I have an additional question regarding my problem: I had the session log itself out yesterday morning, and the logout request was not acknowledged by the counter party. My sessions are configured to start at 5 AM. At 5 AM, the logout messages are continuing to be sent out by the engine. The session is not being recreated, just the messages are not being sent until that point. What is the relation between the session start time and the session creation logic? Would it be possible that the logic for determining the start and end time for the messages has become disconnected from the actual session reset logic? Thanks Jonathan Steinberg -----Original Message----- From: Oren Miller [mailto:or...@qu...] Sent: Tuesday, February 28, 2006 7:45 PM To: Steinberg, Jonathan Cc: John Hensley; qui...@li... Subject: Re: [Quickfix-developers] Session Resetting Well it can happen if the counterparty requests a sequence reset on logon. Doesn't seem to be the likely cause in this case. It happens when the session time expires as you know. There is also a reset method and methods to set the sequence numbers which can be called by anyone. I'll investigate the code to see if there is some other possibility. Hopefully your logs can be used to create a test case which might expose something. --oren Steinberg, Jonathan wrote: >It happens sporadically. I can't reproduce it at will. > >It happened on 2/24/06 at 11:58 am for both of the sessions I have set >up, and again today (2/28) at 9:43 am for one session, and at 2:30 Pm >for another session >It could certainly have been some problem in my application, but I can't >find out what it is. I am really looking for ideas as to where to look; >It would be helpful to know what else would cause a logout/reset to >happen, other than the session times defined in the config file. > >Thanks again > >Jonathan Steinberg > > >-----Original Message----- >From: Oren Miller [mailto:or...@qu...] >Sent: Tuesday, February 28, 2006 12:57 PM >To: Steinberg, Jonathan >Cc: John Hensley; qui...@li... >Subject: Re: [Quickfix-developers] Session Resetting > >How often does this happen Jonathan. Is it repeatable? Does it happen >everyday? > >--oren > >Steinberg, Jonathan wrote: > > > >>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... >><mailto: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 >> >> >> > > > > |
|
From: Steinberg, J. <Jon...@bo...> - 2006-03-02 02:24:12
|
I am wondering if the problem I am having is caused by the creation date
in my session store.
It appears that if the current UTC time is greater than one day than the
creation time, it will reset under certain conditions.
00097
00098 bool SessionTime::isSameSession( const UtcTimeOnly& start,
00099 const UtcTimeOnly& end,
00100 const UtcTimeStamp& time1,
00101 const UtcTimeStamp& time2 )
00102 { QF_STACK_PUSH(SessionTime::isSameSession)
00103
00104 if ( !isSessionTime( start, end, time1 ) ) return false;
00105 if ( !isSessionTime( start, end, time2 ) ) return false;
00106
00107 if ( time1 == time2 ) return true;
00108
00109 UtcDate time1Date( time1 );
00110 UtcDate time2Date( time2 );
00111
00112 if ( start < end || start == end )
00113 return time1Date == time2Date;
00114 else if( start > end )
00115 return labs(time1 - time2) < UTC_DAY;
00116 return false;
00117
Now, if my current time is a day later than the creation time, it will
reset.
I have been using a MS SQLServer store implementation, copied from the
MySqlStore, and the problem may be there. This is in conjunction with
the fact that my service has gotten bounced at odd hours in the past,
which may have caused the creation times to be wacky.
I will monitor the session creation times, and see if this was indeed
the problem.
Jonathan Steinberg
-----Original Message-----
From: Steinberg, Jonathan
Sent: Wednesday, March 01, 2006 3:06 PM
To: 'Oren Miller'
Cc: John Hensley; qui...@li...
Subject: RE: [Quickfix-developers] Session Resetting
I have an additional question regarding my problem:
I had the session log itself out yesterday morning, and the logout
request was not acknowledged by the counter party. My sessions are
configured to start at 5 AM. At 5 AM, the logout messages are continuing
to be sent out by the engine. The session is not being recreated, just
the messages are not being sent until that point.
What is the relation between the session start time and the session
creation logic?
Would it be possible that the logic for determining the start and end
time for the messages has become disconnected from the actual session
reset logic?
Thanks
Jonathan Steinberg
-----Original Message-----
From: Oren Miller [mailto:or...@qu...]
Sent: Tuesday, February 28, 2006 7:45 PM
To: Steinberg, Jonathan
Cc: John Hensley; qui...@li...
Subject: Re: [Quickfix-developers] Session Resetting
Well it can happen if the counterparty requests a sequence reset on
logon. Doesn't seem to be the likely cause in this case. It happens
when the session time expires as you know. There is also a reset method
and methods to set the sequence numbers which can be called by anyone.
I'll investigate the code to see if there is some other possibility.
Hopefully your logs can be used to create a test case which might expose
something.
--oren
Steinberg, Jonathan wrote:
>It happens sporadically. I can't reproduce it at will.
>
>It happened on 2/24/06 at 11:58 am for both of the sessions I have set
>up, and again today (2/28) at 9:43 am for one session, and at 2:30 Pm
>for another session
>It could certainly have been some problem in my application, but I
can't
>find out what it is. I am really looking for ideas as to where to
look;
>It would be helpful to know what else would cause a logout/reset to
>happen, other than the session times defined in the config file.
>
>Thanks again
>
>Jonathan Steinberg
>
>
>-----Original Message-----
>From: Oren Miller [mailto:or...@qu...]
>Sent: Tuesday, February 28, 2006 12:57 PM
>To: Steinberg, Jonathan
>Cc: John Hensley; qui...@li...
>Subject: Re: [Quickfix-developers] Session Resetting
>
>How often does this happen Jonathan. Is it repeatable? Does it happen
>everyday?
>
>--oren
>
>Steinberg, Jonathan wrote:
>
>
>
>>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...
>><mailto: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
>>
>>
>>
>
>
>
>
|
