Thread: RE: [Quickfix-developers] QuickFIX/J mystery....
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-developers
|
From: Shepheard, T. (London) <Tob...@ml...> - 2005-12-19 10:16:24
|
What version are you using? You might want to try the latest code from CVS if you're not already, as there have been some changes maade since the last beta release. No promises that it holds a fix, but there were some changes around the connectivity and session code. -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Tom Dilatush Sent: 16 December 2005 21:31 To: QuickFIX Developers Subject: [Quickfix-developers] QuickFIX/J mystery.... QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX Support: http://www.quickfixengine.org/services.html Hi, folks... Any insight into this strangeness would be very welcome... I have a QuickFIX/J application that is working, but only when I put=20 some baling wire and chewing gum (a hack) into it. This application has a single initiator session, and I've used ThreadedSocketInitiator. =20 Without the hack, on startup the following sequence occurs (via network=20 sniffer): -- a TCP connection is established -- the TCP connection is taken down (and the debug log shows a=20 "responder: disconnect" event). The takedown is initiated by my=20 application's side of the connection. -- the above two sequences are repeated, exactly -- a TCP connection is established for the third time, stays=20 established, but then nothing else happens. Even a logon() call has no=20 effect. If I run the same exact code with a debugger (I'm using IntelliJ Idea),=20 and if I single-step over the call to initiator.start(), and if I have=20 other threads suspended while single-stepping (all three conditions are=20 necessary), then everything works just like you'd expect -- the=20 connection at the TCP level is established on the first try, and the=20 logon proceeds normally.=20 While putzing around trying to imagine what the heck this could be, I=20 discovered the hack: if I insert a delay (a sleep()) of 350 milliseconds or greater in the onCreate(SessionID) method of my Application, then=20 everything works great, first time, every time. Does this ring a bell with anyone? BTW, I'm a newbie on QuickFIX/J, so don't dismiss any bozo maneuvers by=20 saying to yourself "Nah, nobody could be that stupid!" Because yes I could. Thanks, Tom... ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers -------------------------------------------------------- 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/ -------------------------------------------------------- |
|
From: Tom D. <to...@di...> - 2005-12-19 13:03:14
|
Hi, Toby... I'm using "almost the latest" -- checked it out of CVS in early November... Tom... Shepheard, Toby (London) wrote: > What version are you using? You might want to try the latest code from > CVS if you're not already, as there have been some changes maade since > the last beta release. No promises that it holds a fix, but there were > some changes around the connectivity and session code. > > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On Behalf Of > Tom Dilatush > Sent: 16 December 2005 21:31 > To: QuickFIX Developers > Subject: [Quickfix-developers] QuickFIX/J mystery.... > > > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > Hi, folks... > > Any insight into this strangeness would be very welcome... > > I have a QuickFIX/J application that is working, but only when I put > some baling wire and chewing gum (a hack) into it. This application has > > a single initiator session, and I've used ThreadedSocketInitiator. > Without the hack, on startup the following sequence occurs (via network > sniffer): > -- a TCP connection is established > -- the TCP connection is taken down (and the debug log shows a > "responder: disconnect" event). The takedown is initiated by my > application's side of the connection. > -- the above two sequences are repeated, exactly > -- a TCP connection is established for the third time, stays > established, but then nothing else happens. Even a logon() call has no > effect. > > If I run the same exact code with a debugger (I'm using IntelliJ Idea), > and if I single-step over the call to initiator.start(), and if I have > other threads suspended while single-stepping (all three conditions are > necessary), then everything works just like you'd expect -- the > connection at the TCP level is established on the first try, and the > logon proceeds normally. > > While putzing around trying to imagine what the heck this could be, I > discovered the hack: if I insert a delay (a sleep()) of 350 milliseconds > > or greater in the onCreate(SessionID) method of my Application, then > everything works great, first time, every time. > > Does this ring a bell with anyone? > > BTW, I'm a newbie on QuickFIX/J, so don't dismiss any bozo maneuvers by > saying to yourself "Nah, nobody could be that stupid!" Because yes I > could. > > Thanks, > Tom... > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > -------------------------------------------------------- > > 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/ > -------------------------------------------------------- > |
|
From: Tom D. <to...@di...> - 2005-12-19 15:02:14
|
Good idea -- unfortunately, it had no effect on the problem. Still works with my hack, though... I don't think this should matter, but just in case: one thing that may be unusual about my environment is that I'm running Java 5.0 (aka 1.5, aka "Tiger") on the client (initiator) side of this. Tom... Shepheard, Toby (London) wrote: > What version are you using? You might want to try the latest code from > CVS if you're not already, as there have been some changes maade since > the last beta release. No promises that it holds a fix, but there were > some changes around the connectivity and session code. > > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On Behalf Of > Tom Dilatush > Sent: 16 December 2005 21:31 > To: QuickFIX Developers > Subject: [Quickfix-developers] QuickFIX/J mystery.... > > > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > Hi, folks... > > Any insight into this strangeness would be very welcome... > > I have a QuickFIX/J application that is working, but only when I put > some baling wire and chewing gum (a hack) into it. This application has > > a single initiator session, and I've used ThreadedSocketInitiator. > Without the hack, on startup the following sequence occurs (via network > sniffer): > -- a TCP connection is established > -- the TCP connection is taken down (and the debug log shows a > "responder: disconnect" event). The takedown is initiated by my > application's side of the connection. > -- the above two sequences are repeated, exactly > -- a TCP connection is established for the third time, stays > established, but then nothing else happens. Even a logon() call has no > effect. > > If I run the same exact code with a debugger (I'm using IntelliJ Idea), > and if I single-step over the call to initiator.start(), and if I have > other threads suspended while single-stepping (all three conditions are > necessary), then everything works just like you'd expect -- the > connection at the TCP level is established on the first try, and the > logon proceeds normally. > > While putzing around trying to imagine what the heck this could be, I > discovered the hack: if I insert a delay (a sleep()) of 350 milliseconds > > or greater in the onCreate(SessionID) method of my Application, then > everything works great, first time, every time. > > Does this ring a bell with anyone? > > BTW, I'm a newbie on QuickFIX/J, so don't dismiss any bozo maneuvers by > saying to yourself "Nah, nobody could be that stupid!" Because yes I > could. > > Thanks, > Tom... > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > -------------------------------------------------------- > > 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/ > -------------------------------------------------------- > |
