Re: [Quickfix-users] in-session logon (for CME iLink)

[QM <eqm...@nw...>]

Problem solved.  Had to modify QuickFIX to make it work.  (I hope to
release a formal patch down the line, stay tuned.)


On Tue, May 15, 2012 at 8:25 PM, QM <eqm...@nw...> wrote:

> Hello
>
> Has anyone here implemented in-session logon for CME iLink?  Are you able
> to do it in your app code, or did you have to modify QuickFIX itself?
>
> I'm pretty close to doing it in-app but I've hit an issue:
>
> - per the iLink docs, I send the test request, wait for the heartbeat
> response, and send the logon message (141-ResetSeqNumFlag=Y,
> 34-SequenceNum=1)
>
> - also per the iLink docs, CME responds with a logon confirmation that
> sets 141-ResetSeqNumFlag=Y and 34-SequenceNum=1
>
> For that second step, QuickFIX is expecting CME's sequence number to be 2
> instead of 1.  That triggers a disconnect, and the logout message contains
> the reason: "MsgSeqNum too low, expecting 2 but received 1."
>
> Is there a way to stop QuickFIX from disconnecting at this point, and/or
> force the expected sequence number to 1?
>
> (I've tried calling Session::setNextTargetMsgSeqNum( 1 ) after sending out
> the logon message, but to no avail.  I also intercepted the outgoing logout
> message in toAdmin() and rewrote it as a heartbeat, but QuickFIX
> disconnects anyhow.)
>
> Thanks.
>