Re: [Quickfix-developers] Problem exiting onRun

[David M. <dav...@ds...>]

Hi Gene et al

Just downloaded the latest 1.4.1 quickfix.  It now works great!  No more=20
core/errors etc.

Thanks a lot for the help.

David

On Friday 11 Apr 2003 2:22 am, Gene Gorokhovsky wrote:
> Which version of QF are you using? I checked in a
> patch recently that fixed shutdown thread leaks (onRun
> and socket connection threads). I believe Oren
> incorporated it into QF 1.4.1.
>
> Gene
>
> --- David Monheit <dav...@ds...> wrote:
> > Hi All,
> >
> > I have got my java engine running very nicely.
> > Basically I have a market data
> > feed running on a thread and a scheduler running
> > several threads.  The data
> > feed calls a onMarketDataEvent callback and the
> > scheduler calls a onTimerEvent
> > callback.  These callbacks are implemented by my
> > Application (along with all
> > the QF callbacks).
> >
> > On the constructor of the Application object I
> > instatiate and fire up both the
> > market data source and the scheduler.
> >
> > The engine does its thing beautifully.
> >
> > After the specified time, the scheduler calls the
> > onTimerEvenet callback which
> > signals my engine (the Application) to stop.
> >
> > The callback sets quit =3D true which causes onRun to
> > exit it's main loop.
> >
> > onRun nows closes the market data source (I see its
> > threads disappear in the
> > debugger) and it also closes the scheduler (threads
> > also gone).
> >
> > I still see the Main thread, the onRun thread and
> > another application thread
> > which I don't know who created :-(  Is this correct?
> >  Does QF create three
> > threads?  Does the SocketInitiator have a thread
> > besides the onRun?  There are
> > several more System threads but these are owned by
> > the JVM.
> >
> > Anyways, when onRun exits, I get a signal 11
> > (SIGSEV) and the jvm goes to lala
> > land :-(
> >
> > The main thread (which created the Application and
> > invoked the
> > SocketInitiator.start() ) never exits (I have a
> > println just before main()
> > exits, which I never see).
> >
> > Has anyone seen this?  Any ideas?
> >
> > Thanks David.
> >
> > PS Does QF support the creation of dynamic fix
> > sessions? ie the way I see it
> > today, all the sessions I use must be defined in
> > both the Acceptor and the
> > Initiator cfg files.  What if I wanted to create a
> > session to an Acceptor
> > which "was not expecting" me (no entry for me as a
> > TargetCompID in its cfg
> > file).
> >
> > Cheers
>
> -------------------------------------------------------
>
> > This SF.net email is sponsored by: Etnus, makers of
> > TotalView, The debugger
> > for complex code. Debugging C/C++ programs can leave
> > you feeling lost and
> > disoriented. TotalView can help you find your way.
> > Available on major UNIX
> > and Linux platforms. Try it free. www.etnus.com
> > _______________________________________________
> > Quickfix-developers mailing list
> > Qui...@li...
>
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
> http://tax.yahoo.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView, The debu=
gger
> for complex code. Debugging C/C++ programs can leave you feeling lost a=
nd
> disoriented. TotalView can help you find your way. Available on major U=
NIX
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers

--=20
"Cuius testiculus habes, habeas cardium et cerebellum" - Terry Pratchett