Re: [Quickfix-developers] stop/start session programmatically

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Thanks .. .will do...

On 8/24/05, Oren Miller <or...@qu...> wrote:
> Well first of all if you are doing anything with sequence resets, you sho=
uld
> be using the latest 1.10.2.  Anything earlier didn't really have full
> support for sequence resets.
>=20
> Now, if you want to send a logon with a sequence reset, just add it to th=
e
> logon message in the toAdmin call.  QuickFIX should then take care of all
> the necessary sequence reset operations automatically.  You should never
> have to instantiate a new SocketInitiator.  It is designed to recover fro=
m
> all scenarios.
>=20
> --oren
>=20
> ----- Original Message -----
> From: "VP Marketing IT Asset Enterprise Technologies" <ass...@gm...=
m>
> To: "Oren Miller" <or...@qu...>
> Cc: "Alvin Wang" <AW...@ff...>; "Caleb Epstein"
> <cal...@gm...>; <qui...@li...>;
> <qui...@li...>
> Sent: Wednesday, August 24, 2005 10:16 AM
> Subject: Re: [Quickfix-developers] stop/start session programmatically
>=20
>=20
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>=20
> This discussion has been quite useful.
> Please consider the following scenario:
>=20
> State:
> Due to sequence number mismatch, a logon message is refused.
> The counterparty actually disconnects. Consequently there is no
> session.
>=20
> Objective: Send a Logon (which presupposes a Session (new one) is created
> for that counterparty) perhaps with tag 141 set to 'Y'.
>=20
> After reviewing SessionSettings, Session, Logon/Message/MessageFactory...
> I am still not clear about this.
> Is it recommended that I instantiate SocketInitiator from scratch?
> If so how can I pass the tag 141 related information.
> Session does not declare a constant for 141.
>=20
> thank you for your time and suggestion.
> --
>=20
>=20
> On 8/16/05, Oren Miller <or...@qu...> wrote:
> > QuickFIX Documentation:
> > http://www.quickfixengine.org/quickfix/doc/html/index.html
> > QuickFIX Support: http://www.quickfixengine.org/services.html
> >
> > Yeah, but this and the ResetOnDisconnect were originally put in
> > because it is a convenient way to reset the system between acceptance
> > tests.  People have found them useful for various things (such as
> > market data distribution where you don't care for resends and
> > resetting the sequence numbers is convenient).  Basically it's nice
> > for internal systems where you want to pass things around, but they
> > are not transactional, and you don't really care about FIX's
> > guaranteed delivery.  In reality I would not expect such a
> > configuration to be used in a publicly exposed FIX session,
> > particularly one which contains order routing traffic.
> >
> > --oren
> >
> > On Aug 16, 2005, at 4:59 PM, Alvin Wang wrote:
> >
> > >
> > > I do not think this is default. But for example, QF has
> > > ResetOnLogout configuration
> > >
> > >
> > >
> > >
> > > "Oren Miller" <or...@qu...>
> > > 08/16/2005 05:18 PM
> > >
> > >
> > >         To:        "Alvin Wang" <AW...@FF...>
> > >         cc:        "Caleb Epstein" <cal...@gm...>,
> > > <qui...@li...>, <quickfix-developers-
> > > ad...@li...>
> > >         bcc:
> > >         Subject:        Re: [Quickfix-developers] stop/start
> > > session programmatically
> > >
> > >
> > >
> > > Do you have reason to believe this is the case?  It would be non-
> > > standard behavior.
> > >
> > > --oren
> > > ----- Original Message -----
> > > From: Alvin Wang
> > > To: Oren Miller
> > > Cc: Caleb Epstein ; qui...@li... ;
> > > qui...@li...
> > > Sent: Tuesday, August 16, 2005 4:47 PM
> > > Subject: Re: [Quickfix-developers] stop/start session programmaticall=
y
> > >
> > >
> > > I see.
> > >
> > > But will it send logout msg? Some counterparty may configure to
> > > reset seq number on receiving logout msg.
> > >
> > >
> > >
> > > "Oren Miller" <or...@qu...>
> > > 08/16/2005 05:07 PM
> > >
> > >
> > >        To:        "Caleb Epstein" <cal...@gm...>, "Alvin
> > > Wang" <AW...@FF...>
> > >        cc:        <qui...@li...>,
> > > <qui...@li...>
> > >         bcc:
> > >        Subject:        Re: [Quickfix-developers] stop/start session
> > > programmatically
> > >
> > >
> > >
> > >
> > > No, it does not reset sequence numbers.
> > >
> > > --oren
> > > ----- Original Message -----
> > > From: Alvin Wang
> > > To: Caleb Epstein
> > > Cc: Oren Miller ; qui...@li... ;
> > > qui...@li...
> > > Sent: Tuesday, August 16, 2005 4:37 PM
> > > Subject: Re: [Quickfix-developers] stop/start session programmaticall=
y
> > >
> > >
> > > session.logout()  will send logout msg and reset seq number to 1,
> > > right? But i only want to stop and restart later. I do not want to
> > > reset seq number (and send logout msg)..
> > >
> > >
> > > Caleb Epstein <cal...@gm...>
> > > 08/16/2005 04:53 PM
> > >
> > >
> > >       To:        Alvin Wang <AW...@ff...>
> > >       cc:        qui...@li...,
> > > qui...@li..., Oren Miller
> > > <or...@qu...>
> > >       bcc:
> > >        Subject:        Re: [Quickfix-developers] stop/start session
> > > programmatically
> > >
> > >
> > >
> > >
> > >
> > > On 8/16/05, Alvin Wang <AW...@ff...> wrote:
> > >
> > > > Are there any APIs so that QF can stop/restart just a specific
> > > session
> > > > programmatically between start time and end time?
> > >
> > > Session::logout will effectively stop the session.  If the session is
> > > logged on, it will logout and disconnect cleanly.  Then, if it is an
> > > Initiator, it will stop connecting to the counterparty; and if it is
> > > an Acceptor, it will refuse Logon attempts from the counterparty.  Yo=
u
> > > can re-enable with Session::logon
> > >
> > > --
> > > Caleb Epstein
> > > caleb dot epstein at gmail dot com
> > >
> > >
> > > *********************************************************************=
*
> > >  This e-mail message is intended solely for the use of the
> > > addressee. The message may contain information that is privileged
> > > and confidential. Disclosure to anyone other than the intended
> > > recipient is prohibited. If you are not the intended recipient,
> > > please do not disseminate, distribute or copy this communication,
> > > by e-mail or otherwise. Instead, please notify us immediately by
> > > return e-mail (including the original message with your reply) and
> > > then delete and discard all copies of the message. We have taken
> > > precautions to minimize the risk of transmitting software viruses
> > > but nevertheless advise you to carry out your own virus checks on
> > > any attachment to this message. We accept no liability for any loss
> > > or damage caused by software viruses.
> > > *********************************************************************=
*
> > >
> > >
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> > Practices
> > Agile & Plan-Driven Development * Managing Projects & Teams * Testing &=
 QA
> > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5=
sf
> > _______________________________________________
> > Quickfix-developers mailing list
> > Qui...@li...
> > https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> >
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>=20
>