[Quickfix-developers] RE: Logout reason

[Francis G. <fr...@at...>]

Oren,

You're right QF did send a resend request but the counterparty closed the
socket so I didn't notice.  (see log below)

The "sequence number too high" message is from the client (initiator) point
of view.  It appears that the counterparty does not send a logoff or a
session rejection message; it just closes the socket when it receives a
MsgSeqNum that is lower than what it expects.  BTW it's not a QF acceptor
but a custom 3rd party server.

This is why the only solution I see is to increase the
setNextSenderMsgSeqNum by 1000 every time the socket drops during logon, but
I'm not comfortable with such a kludge; what if there are other conditions
that cause the socket to drop?  Comments welcome.

So to conclude, it does not appear to be a QF issue after all because the
acceptor side does not send any notification that the logon failed.

20050613-20:26:19 : Created session
20050613-20:26:19 : Connecting to 127.0.0.1 on port 10501
20050613-20:26:19 : Connection succeeded
20050613-20:26:19 : Initiated logon request
20050613-20:26:19 : Received logon response
20050613-20:26:19 : MsgSeqNum too high, expecting  1 but received 481
20050613-20:26:19 : Socket Error: Connection reset by peer.
20050613-20:26:19 : Disconnecting
20050613-20:26:19 : Sent ResendRequest FROM: 1 TO: 0

Thanks,

Francis