|
From: Shepheard, T. \(London\) <Tob...@ml...> - 2007-03-12 15:46:29
|
I don't have an answer for you, but can say that I've run QFJ without problems under the Eclipse debugger so it definitely does work. I've used JDK 1.4 and 1.5, but haven't tried with 1.6. I also tried adding a System.in.read() after my start() method (albeit, I didn't have a stop immediately after), and that worked fine. Apologies if some of these questions seem a bit trivial, but I figure it's always worth checking... Just to be sure there's nothing silly going on, have you checked in the Eclipse debug mode that none of the threads are paused or blocked that shouldn't be? I've been stupid enough before now to forget about a breakpoint I've put in on a previous occasion, and I'd like to think I'm not the only one :) If it's not a breakpoint, is it possible you have a thread-lock situation? The timing in debug mode may be different enough to show up a problem that wouldn't occur normally. Does the application still wait for something on System.in or is it exiting immediately when in debug mode, i.e. is it as if it's grabbing the input right away from the console when in debug mode? Are you checking the read() call for exceptions for any issues there? It might be worth printing out whatever's read in by System.in.read(), in case Eclipse in debug mode is doing anything here. Regards Toby -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Bud Bach Sent: 09 March 2007 21:47 To: qui...@li... Subject: [Quickfixj-users] Different results under Eclipse Run vs Debug QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ QuickFIX/J Support: http://www.quickfixj.org/support/ I'm experiencing some weirdness running my application within Eclipse. When I run under the debugger (Debug As...), my application works as I expect. When I call initiator.start(), quickfixj initiates a logon to the counterparty and everything seems to go well. When I run the application (Run As...), the session appears to start but quickfixj does not initiate a login sequence. Is it something to do with the blocking call to System.in.read() after I start the initiator?=20 initiator =3D new ThreadedSocketInitiator(application, messageStoreFactory, settings, logFactory, messageFactory); initiator.start(); System.out.println("press <enter> to quit"); System.in.read(); initiator.stop(); System.exit(0); Thanks. -- Bud ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ Quickfixj-users mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfixj-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the = sender, delete it and do not read, act upon, print, disclose, copy, = retain or redistribute it. Click here for important additional terms = relating to this e-mail. http://www.ml.com/email_terms/ -------------------------------------------------------- |