Re: [Quickfix-developers] Socket Error when expecting a Logout message response
Brought to you by:
orenmnero
From: Shane T. <str...@co...> - 2008-03-12 21:55:57
|
Yoav, You should send a Session.lookupSession(SessionID).logout() to force the logout and wait for a little while (possibly 30 seconds) using a loop similar to this: int ALITTLEWHILE = 30; for (int sec = 1; (sec <= ALITTLEWHILE) && Session.lookupSession(SessionID).isLoggedOn(); sec++) { Thread.Sleep(1000); } initiator.stop(); -- Shane Trotter Connamara Systems, LLC On 3/12/08, Yoav <yo...@ya...> wrote: > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > QuickFix version 1.12.4 (C++), Solaris 10 > > I'm implementing a clean shutdown in my FIX client. > When the process is being killed I send Logout message > on all my QF Initiator sessions. > > I see the following problem: > Sometimes everything works, meaning: I see the Logout > message being sent and the response being received. > But sometimes I see the Logout message being sent and > immediately I see an error: > "(Socket Error: Connection reset by peer.)" > > 2 comments: > 1) The 'peer' in my case is 'stunnel' which is doing > port forwarding > 2) During the time I kill my FIX process there are > incoming messages (MarketDataSnapshotFullRefresh) > > Any clue will be highly appreciated, > Yoav > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > |