The following code in SocketEngine has a bug you should be aware of. It's a simple typo where I mixed up In and Out.
public void ResetMsgSeqNumIn(int iMsgSeqNumIn) { if (!_bInitialized) throw new Exception("Must be initialized to reset the MsgSeqNum in");
if (_bConnect || _bLogon) throw new Exception("Must be disconnected to reset the MsgSeqNum int");
_messageCache.ResetMsgSeqNumOut(iMsgSeqNumIn); _iMsgSeqNumIn = iMsgSeqNumIn; }
Change to the following: _messageCache.ResetMsgSeqNumIn(iMsgSeqNumIn);
Log in to post a comment.
The following code in SocketEngine has a bug you should be aware of. It's a simple typo where I mixed up In and Out.
public void ResetMsgSeqNumIn(int iMsgSeqNumIn)
{
if (!_bInitialized)
throw new Exception("Must be initialized to reset the MsgSeqNum in");
if (_bConnect || _bLogon)
throw new Exception("Must be disconnected to reset the MsgSeqNum int");
_messageCache.ResetMsgSeqNumOut(iMsgSeqNumIn);
_iMsgSeqNumIn = iMsgSeqNumIn;
}
Change to the following:
_messageCache.ResetMsgSeqNumIn(iMsgSeqNumIn);