RE: [Quickfix-developers] RE: In-Session Logon to Reset SequenceNumber

[Jain, A. <Ani...@rb...>]

Hi Oren,
Today while attempting an In-session logon to CME to reset sequence numbers=
 to (1,1), the QuickFIX engine logged itself out with the message:

	MsgSeqNum too low, expecting 2 but received 1

I found that the problem comes when a sequence reset logon is being sent, a=
nd just before it, QuickFIX engine receives a test request by the exchange.

At logon reset request, QuickFIX engine resets the exchange sequence number=
 to 1 ( And not when the exchange accepts the reset and sends a conformatio=
n!)

So, after request has been made, and before a response to it has been recei=
ved, the QuickFIX engine immediately processes the exchange's earlier test =
request by sending a heartbeat and increases the exchange sequence number t=
o 2 (:`(. The fact is that the test request was made under previous logon r=
egime, with different sequence number. And the sequence number being increm=
ented is unrelated to the previous one.

When the logon reset conformation from exchange comes, the sequence number =
has already been increased to 2 - invalidating the exchange's sequence numb=
er of 1.

This is just a small crib to a great product! I resolved it by suspending r=
eset logon in this case till a heartbeat has been received in fromAdmin.

Thanks.

Anil Jain

=20

=20

=20

_______________________________________________________________________

This E-Mail (including any attachments) may contain privileged or confident=
ial information.  It is intended only for the addressee(s) indicated above.
The sender does not waive any of its rights, privileges or other protection=
s respecting this information. =20
Any distribution, copying or other use of this E-Mail or the information it=
 contains, by other than an intended recipient, is not sanctioned and is pr=
ohibited.
If you received this E-Mail in error, please delete it and advise the sende=
r (by return E-Mail or otherwise) immediately.

This E-Mail (including any attachments) has been scanned for viruses.=20
It is believed to be free of any virus or other defect that might affect an=
y computer system into which it is received and opened.=20
However, it is the responsibility of the recipient to ensure that it is vir=
us free.=20
The sender accepts no responsibility for any loss or damage arising in any =
way from its use.

E-Mail received by or sent from RBC Capital Markets is subject to review by=
 Supervisory personnel.=20
Such communications are retained and may be produced to regulatory authorit=
ies or others with legal rights to the information.