|
From: Steve B. <st...@te...> - 2007-09-17 23:35:53
|
Hi Toli, This is a vague area of the spec. The specification says the test request should be sent after the missed heartbeat plus "some reasonable transmission time". The definition of reasonable is left to the implementer. QF and QFJ consider 50% of the heart beat interval to be reasonable. Apparently TransactTools uses 30%. If you want to submit a patch to make this configurable, I'll add it although it will probably only be used for OpenFix certification. IIRC, there are several other tests that fail because of differing interpretation of ambiguous areas of the specification. Regards, Steve > -----Original Message----- > From: qui...@li... [mailto:quickfixj- > use...@li...] On Behalf Of Toli Kuznets > Sent: Monday, September 17, 2007 3:41 PM > To: qui...@li... > Subject: [Quickfixj-users] Question about calculating time to send a > TestRequest message > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Hey, > > I also posted this as a JIRA question 236: > http://www.quickfixj.org/jira/browse/QFJ-236 > > We've been going through a certification process with TransactTools > (http://www.openfix.net/), and encountered a different expected > behaviour with sending Test Requests. > > In the TransactTools test, they skip a heartbeat message and expect > our quickfix engine (Ie QFJ) to send a test request: > "We suppressed our last heartbeat message. > In response we expected to receive a test request message from you > within 9 seconds (30% of the HeartBeatInt field) but did not." > > Seems like they expect it to be sent within HeartBeatInt+9secs. > Looking at the code in SessionState.isTestRequestNeeded(), it > calculates the Test Request delay as 1.5 * (HeartBeatInt + > numTestRequestsSent + 1), which translates into HeartBeatInt * 1.5 > (for first request) = 30 + 15secs, which is over the +9 seconds that's > expected. > > Is there a known spec for this formula or was it something > "reasonable" but not necessarily standard? Maybe it's something we > need to make configurable to satisfy different expectations form > counterparties? > > thoughts? > > -- > Toli Kuznets > http://www.marketcetera.com: Open-Source Trading Platform > download.run.trade. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users |