Re: [Quickfix-developers] What should be done if ResendRequest generated by doTargetTooHigh have ne
Brought to you by:
orenmnero
From: len <le...@fa...> - 2006-08-24 18:09:57
|
Hi, I have tested 1.12.2 in regards of the bug when Session was not timing = out when no messages in the right order were coming (although messages with = too high sequence number kept coming) 1.11.1 version in such condition stuck = in the loop insisting that it already sent ResendRequest. In regards of testing: I have simulated the same conditions and it DID = work as advertised. After two-something heartbeats the session was = automatically logged of with event "Timed out waiting for heartbeat". Thank you guys = you have saved me from putting in na=EFve hack. By the way I also have posted a question about delayed logon and pending connections under different name - I have a hard time to reply to this = news group - even though I have registered with it. Len. -----Original Message----- From: Caleb Epstein [mailto:cal...@gm...]=20 Sent: Monday, August 21, 2006 4:26 PM To: Joerg Thoennes Cc: len; qui...@li... Subject: Re: [Quickfix-developers] What should be done if ResendRequest generated by doTargetTooHigh have never been received or acted upon On 8/21/06, Joerg Thoennes <Joe...@ma...> wrote: > > We recently encounter the situation when remote FIX engine seems to ignore > > ResendRequest message generated by our QuickFix engine. = Unfortunately that > > ultimately blocked our running QuickFix engine because remote party = was keep > > sending messages with higher and higher sequence numbers and = QuickFix simply > > queue the message and just log ""Already sent ResendRequest FROM:.". > > Therefore Application code was not aware about problem and QuickFix = did not > > try to resolve it. > > > > Did anyone have experience with it? What solution should be? I am inclining > > to add some time-out check (basically add time when resendRequest = was sent > > into m_state and resend the message after certain period of time). = May be > > upcoming QuickFix releases address this problem? > > reading the discussion in the FIX Protocol forums, I would like to = support John Prewetts suggestion > to force a logout (or disconnect) after a time-out. Oren, do you think = it is worth to add > configuration option as "ResendTimeout" to support this? What version of QF are people testing this behavior with? I think the very latest release 1.12.2 (and anything built from the SVN sources after 4/29/06 (r1437)) will timeout the connection when this happens and no new code or configuration should be necessary to support it. It would be great if someone could test this. There *was* a bug where the Session's lastReceived timestamp was being updated before the sequence number checking was done, which caused test requests never to go out and the connection to stay alive in this scenario. this bug was fixed in April, but there haven't been any QuickFIX releases since then ((until last week). See my email about this from July 20. http://sourceforge.net/mailarchive/message.php?msg_id=3D32260466 --=20 Caleb Epstein |