|
From: Steve B. <st...@te...> - 2007-03-09 23:11:24
|
Hi Bud, I don't know any reason why System.in.read() would block the session logon. You could run your application in Java 5 or 6, connect with JConsole and look at the thread state. That would probably give you a good idea of the cause of the blocking. With Java 6 you don't need any special system properties to enable the JMX access to the JVM platform MBeans from JConsole. Just run normally from Eclipse, start JConsole, and connect to your process. With Java 5 you need to add -Dcom.sun.management.jmxremote to your VM arguments. Steve > 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? > > initiator = 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=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |