Re: [Quickfix-users] Query on QuickFIX 1.9.3 Version --Oren
Brought to you by:
orenmnero
|
From: Oren M. <or...@qu...> - 2004-11-10 21:04:12
|
Dinesh,
No, unfortunately this did not make it into 1.9.3. It will go into the =20=
next release. You will have to apply this patch manually right now.
--oren
On Nov 10, 2004, at 4:54 AM, Dinesh Belaguli wrote:
> Hi oren,
> =A0=A0=A0 The problem mentioned below (i.e., Session Establishment =
when the =20
> startTime is reached)is working fine with Max Solution. so is this fix =
=20
> available in the latest version of quickfix.
> =A0=A0=A0
> thanx
> dinesh.
> -----Original Message-----
> From: Requenes, Max [mailto:Max...@sa...]
> Sent: Monday, November 08, 2004 7:57 PM
> To: Dinesh Belaguli; qui...@li...; =20
> qui...@li...
> Subject: RE: [Quickfix-developers] Sessions are not established when =20=
> it reaches the startTime.
>
> Do you happen to be using ThreadedSocketInitiator?
> =A0
> I ran into a similar problem. I fixed it by modifying =20
> ThreadedSocketInitiator::onStart()
> =A0
> change this:
> connect();
> while ( !m_stop )
> =A0 process_sleep(1);
> =A0
> to this:
>
> while ( !m_stop ) {
> =A0 connect();
> =A0 process_sleep(1);
> }
> =A0
> =A0
> I submitted this fix to the mailing list before, but got no response.
> http://sourceforge.net/mailarchive/forum.php?=20
> thread_id=3D4325707&forum_id=3D103
> =A0
> Let me know if this helps.
> -----Original Message-----
> From: Dinesh Belaguli [mailto:Din...@in...]
> Sent: Monday, November 08, 2004 4:05 AM
> To: qui...@li...; =20
> qui...@li...
> Cc: Dinesh Belaguli
> Subject: [Quickfix-developers] Sessions are not established when it =20=
> reaches the startTime.
> Importance: High
>
>
> hi,
> =A0I have two programmes acting one as client and other as server.
> in the quickfixConfig.cfg (configuration file) i have configured the =20=
> start and EndTime as follows.
>
> StartTime=3D08:45:00
> EndTime=3D08:10:00=A0
>
> the above timings are in GMT.
> for convenience i changed my system time to GMT.
>
> I started the server programme before running the client programme.
>
>
>
> Two cases.
> 1) when i start my client programme before the start Time say 08:40:00
> =A0=A0=A0=A0=A0=A0=A0 connection established successfully but the =
sessions are not =20
> created that is fine.
> =A0=A0=A0=A0=A0=A0=A0 but when the time reaches 8:45 it didn't =
(create) establish =20
> the sessions (ideally it should establish the sessions know.)
>
> =A0=A0=A0=A0=A0=A0=A0
>
> 2) when i start the client programme some where after the startTime =20=
> say 8:48 then it established sessions.
>
> i want to know y the sessions are not created in the first case as i =20=
> have explained..
> can any one through some light on this..
>
>
>
> =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0 BELOW is My Configuration =
File i.e. at client side.
> =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0
>
>
>
> [DEFAULT]
> ConnectionType=3Dinitiator
> HeartBtInt=3D20
> FileStorePath=3Dstore
> FileLogPath=3Dlogs
>
> StartTime=3D08:45:00
> EndTime=3D08:10:00
>
> ResetOnDisconnect=3DN
> ResetOnLogout=3DN
> ProviderPassword=3D
> SenderSubID=3D
> OnLogonResetMsgSeqNo=3Dfalse
>
>
>
> [SESSION]
> BeginString=3DFIX.4.2
> SenderCompID=3DITLClientMD
> TargetCompID=3DITLServer
> UseDataDictionary=3DY
> ValidateFieldsOutOfOrder=3DY
> DataDictionary=3Djava/spec/barclay/FIX42.xml
> CheckLatency=3DN
> SocketConnectHost=3Dlocalhost
> SocketConnectPort=3D5007
>
>
>
>
> [SESSION]
> BeginString=3DFIX.4.2
> SenderCompID=3DITLClientOrder
> TargetCompID=3DITLServer
> UseDataDictionary=3DY
> ValidateFieldsOutOfOrder=3DY
> DataDictionary=3Djava/spec/barclay/FIX42.xml
> CheckLatency=3DN
> SocketConnectHost=3Dlocalhost
> SocketConnectPort=3D5007
>
>
>
> Thanx.
> Dinesh.
>
>
>
>
> DISCLAIMER: This e-mail message and any attachments are intended =20
> solely for the use of the individual or entity to which it is =20
> addressed and may contain information that is confidential or legally =20=
> privileged. If you are not the intended recipient, you are hereby =20
> notified that any dissemination, distribution, copying or other use of =
=20
> this message or its attachments is strictly prohibited. If you have =20=
> received this message in error, please notify the sender immediately =20=
> and permanently delete this message and any attachments.
>
>
|