|
From: Robert N. <rob...@gm...> - 2021-03-26 21:43:17
|
Does anybody know what the typical implementation is when an acceptor has to satisfy a resend request but also send you current message flow. Are there implementations that wait too see if they are going to get a resend request soon after logon before sending you current flow? I’m seeing with quickfixj at least one provider who may not be doing this and it seems to cause issues. where they haven’t fully satisfied by resend request before the begin sending me current messages. That said I don’t have any direct evidence that this is the problem just that only this one provider seems to have difficulty recovering the session and I know in their case they’ve implemented their own fix engine. and since I’m on an older version of quickfixj (1.5.2 with stack overflow resend fix) I’m trying to understand what the limitations are. |