Re: [Quickfixj-users] Quickfixj enqueuing logon and not sure when a resend request is satisfied.

[Robert N. <rob...@gm...>]

That much I get but it keeps track of the requested range and considers the resend request satisfied once it sees a message larger than the range
and then should stop enqueuing the messages.

In this case it received such  message but for some reason it never satisfied the resend request and continued to enqueue everything that was sent
as “current” after the resend request had resent everything in the requested range.

> On Sep 21, 2020, at 10:13 AM, philip <ph...@wh...> wrote:
> 
> In short, it simply expects the next message and stores anything higher. It should tell you what sequence number it's expecting and not been sent:
> 
> https://github.com/quickfix-j/quickfixj/blob/QFJ_RELEASE_1_5_2/core/src/main/java/quickfix/Session.java#L2114
> 
> I do recommend you consider upgrading - there's a couple of resend request bugs fixed - e.g: https://github.com/quickfix-j/quickfixj/pull/48
> 
> Best regards,
> 
> Philip Whitehouse.
> 
> On 2020-09-21 15:00, Robert Nicholson wrote:
>> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
>> QuickFIX/J Support: http://www.quickfixj.org/support/
>> I have an older quickfixj  application that seems to repeatedly have
>> more issues with one vendors traffic than another.
>> This vendor has a custom implementation of their FIX engine and I’m
>> wondering if the problems that result from that are due to quickfixj
>> or their implementation.
>> In the latest episode I have an example where
>> I logon
>> their logon was queued because it was received out of order after a disconnect.
>> our end has sent a resend request
>> their end has sent a resend request
>> then they begin to satisfy the resend request I made with all those
>> message that have posdup = Y
>> at the end they have began sending messages with a 34 that’s 1 more
>> than the 34 they used with their resend request earlier.
>> There is no sequence reset from them at all.
>> At the point quickfixj still doesn’t consider the resend request
>> satisfied and is continuing to enqueue every subsequent message.
>> The version used is older 1.52 with custom patches including the
>> recursive resend request handling to avoid stack overflow.
>> Q. What does quickfixj generally expect to see before it considers a
>> resend request satisfied?
>> _______________________________________________
>> Quickfixj-users mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users