I assume you mean 1.10.2? Yeah, this was a bug that was fixed in
1.11.0. It's fairly harmless. It is simply connecting and
disconnecting immediately. The session is not active, however the
transport is always attempting reconnection and the session then closes
the connection when it is informed that the session is closed. With the
new release, the transport checks if the session is alive before
attempting to connect. I believe the other problem was also fixed in
1.11.0.
--oren
Steinberg, Jonathan wrote:
>10.0.2
>
>
>Jonathan Steinberg
>Client Application Development
>Banc of America Securities, Prime Brokerage Services
>212-583-8762
>
>
>-----Original Message-----
>From: Oren Miller [mailto:or...@qu...]
>Sent: Tuesday, February 14, 2006 2:36 PM
>To: Steinberg, Jonathan
>Cc: qui...@li...
>Subject: Re: [Quickfix-developers] Session Start and end Times
>
>What version of QuickFIX?
>
>--oren
>
>Steinberg, Jonathan wrote:
>
>
>
>>Could someone please clarify the session start and end times?
>>
>>I am using c# (.Net framework 1.1, VS2003) with the quickfix .net
>>wrappers
>>
>>I need to have a session shut down at 9PM for system maintenance, and
>>start up again at Midnight. I am in US Eastern time (GMT-5).
>>
>>According to the documentation, the session start and end times are
>>UTC, so it seems that the session settings should be
>>
>>* *
>>
>>* StartTime=05:00:00*
>>
>>* EndTime=02:00:00*
>>
>>However, in the event logs , at 9PM, I see a continuous stream of
>>
>>Disconnecting
>>
>>Socket Error
>>
>>Connecting to XXX.XXX.XXX.XXX on port YYYY
>>
>>Connection succeeded
>>
>>Disconnecting, etc
>>
>>Until the session I am connecting to goes down at 10:30 when I see
>>
>>Connecting to XXX.XXX.XXX.XXX on port YYYY
>>
>>Connection failed
>>
>>repeated until 5:30 Am when the remote session goes up, and I connect
>>again.
>>
>>Should this be happening? Are the event logs misleading or is the
>>session still active?
>>
>>Another question is that when I try to test the session start and end
>>time behavior locally, with an acceptor and initiator both running on
>>my machine , I am setting the session start and end time as (for
>>example, to start at 1:40 PM)
>>
>>StartTime=18:40:00
>>
>>EndTime=23:00:00
>>
>>The session is idle until 1:40 as expected, but then cannot connect at
>>
>>
>
>
>
>>that time - I see
>>
>>Created session
>>
>>Connecting to localhost on port 6666
>>
>>Connection succeeded
>>
>>Disconnecting
>>
>>Socket Error etc. etc.
>>
>>in the event logs. If I change the session start time to prior to the
>>current time (e.g. 10:00:00) and restart the session it works fine.
>>
>>I would be grateful if someone can explain this behavior or point me
>>to the explanation. I could not find anything in the documentation.
>>
>>Thanks
>>
>>Jonathan Steinberg
>>
>>
>>
>
>
>
>
|
