Re: [Quickfix-developers] QF Java abruptly exits

[Miller, O. <OM...@ri...>]

Yes!  Check the release notes.  Initiator::start and Acceptor::start are =
no longer blocking calls.

It used to be the start would block on onRun, this is no longer the =
case.  Now, start returns immediately giving you full control of the =
main thread, and stop must be called to shut eveything down.

The easiest way to upgrade from 1.4 to 1.5 is to call the code like so.

acceptor.start();
acceptor.onRun();
acceptor.stop();

Then the rest of you application won't know the difference.
--------------------------
Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: C. Johnson <jav...@ce...>
To: qui...@li... =
<qui...@li...>
Sent: Mon Aug 25 17:55:21 2003
Subject: [Quickfix-developers] QF Java abruptly exits

Hi gang-

I recently upgraded to QF 1.5, built everything on Windows XP.

I have a Java acceptor which initiates a connection to a JMS topic
and when I RX NewOrderSingle messages, I place them on the topic.
That's fine.. That connects to JMS provider OK.

But, for some reason, I get these messages, then the app just dies:

<20030825-22:51:04, FIX.4.2:MQGATEWAY-IL-1->TESTCLIENTAPP-1, event>
  (Created session)
<20030825-22:51:04, FIX.4.2:MQGATEWAY-IL-1->TESTSENDER-1, event>
  (Created session)

It creates the sessions, then just exits. Did I miss something
along the way somewhere? Did something change with the threading
from 1.4 to 1.5?

-cedrick



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click =
here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers