Re: [Quickfix-developers] starting and stopping socketInitiator()

[Oren M. <or...@qu...>]

Stopping and restarting initiators doesn't really work right now.  Instead 
you should use the logoff and logon commands on your sessions.

--oren

----- Original Message ----- 
From: "Radhika Sambamurti" <Rad...@Pi...>
To: <qui...@li...>
Sent: Monday, January 03, 2005 10:17 AM
Subject: [Quickfix-developers] starting and stopping socketInitiator()


QuickFIX Documentation: 
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
QuickFIX Support: http://www.quickfixengine.org/services.html

Hi,

I have been able to analyze my session problems to the way I start and
stop socketInitiator().

The first time the app starts - socketInitiator is started and when I
logoff a session, socketInitiator is stopped.
When I start socketInitiator and try to logon, onLogon is not called,
and the session never logs on.
I am not exiting my application when I logoff a session and stop the
SocketInitiator.

I see a few emails about this question. Is anyone starting, stopping,
and starting socketInitiator for every session?

Thanks,
Radhika


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers