[Quickfix-developers] (no subject)

[Martin T. <mta...@ho...>]

Hi Oren,

I found this message when looking for a solution at my issue.  Displayed 
below, is a reply that you sent to Eric.  My issue is very similar to his.

Initially I call initiator.start().  When I want it to disconnect, I call 
initiator.stop(), then, as described by Eric, it hang somewhere 
indefinitely.  I have to kill my app.

I know that I can stop any session by calling session.logout().

So, what I would like to know is the good way of connecting and 
disconnecting.  Is it throught the initiator.start and initiator.stop ? In 
this case, what could make my initiator hang forever?
Or to do a initiator.start initially, and then proceeding per session 
logout/logon ?

Thank you!
Martin


>Why is the initiator thread being terminated?  All you need to do is call 
>logout when you want to disconnect, and call logon when you want to 
>reconnect.  Nothing here should affect your Initiator thread.  Is something 
>else going on?  Did you call stop on the Initiator?
>
>--oren
>
>On Jul 7, 2004, at 4:44 PM, Eric Ginder wrote:
>
> > I"m having trouble with reconnecting after I disconnect a session.  > 
>I"m using Session::logout() to kill the session and I see the logout > 
>message coming back from the targetcomp. The initiator thread that is > 
>supposed to terminate at this point is hanging somewhere and when I > try 
>to reconnect, it fails because the socket initiator is still > waiting for 
>the variable m_stop to turn to true.
> >  > Does anyone else have this problem or is there a better way to > 
>disconnect?
> >  > Thanks,
> >  > Eric Ginder
> > Last Atlantis Capital
> >  ^