Thread: RE: [Quickfix-developers] RE: In-Session Logon to Reset SequenceNumber
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-developers
|
From: Jain, A. <Ani...@rb...> - 2006-01-26 22:45:12
|
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. |
|
From: Fanshteyn, T. <tfa...@bo...> - 2006-01-27 12:43:02
|
I know there are a lot of changes in CVS. Any idea on the timeframe for the next release? -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Oren Miller Sent: Thursday, January 26, 2006 5:51 PM To: Jain, Anil Cc: qui...@li... Subject: Re: [Quickfix-developers] RE: In-Session Logon to Reset SequenceNumber QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX Support: http://www.quickfixengine.org/services.html Anil, There is a fix for this that will be going out with the next release (or in CVS if you are adventurous). Please try it again at that time and let us know if it works correctly. --oren Jain, Anil wrote: > 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, and 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 > conformation!) > > So, after request has been made, and before a response to it has been > received, the QuickFIX engine immediately processes the exchange's > earlier /test request/ by sending a heartbeat and increases the > exchange sequence number to 2 *(:`(*. The fact is that the test > request was made under previous logon regime, with different sequence > number. And the sequence number being incremented 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 number of 1. > > This is just a small crib to a great product! I resolved it by > suspending reset logon in this case till a heartbeat has been received > in fromAdmin. > > Thanks. > > Anil Jain > > > > > > > >_______________________________________________________________________ > >This E-Mail (including any attachments) may contain privileged or confidential information. It is intended only for the addressee(s) indicated above. >The sender does not waive any of its rights, privileges or other protections respecting this information. >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 prohibited. >If you received this E-Mail in error, please delete it and advise the sender (by return E-Mail or otherwise) immediately. > >This E-Mail (including any attachments) has been scanned for viruses. >It is believed to be free of any virus or other defect that might affect any computer system into which it is received and opened. >However, it is the responsibility of the recipient to ensure that it is virus free. >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. >Such communications are retained and may be produced to regulatory authorities or others with legal rights to the information. > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Oren M. <or...@qu...> - 2006-01-27 19:00:41
|
Next week. --oren Fanshteyn, Timur wrote: >QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html >QuickFIX Support: http://www.quickfixengine.org/services.html > >I know there are a lot of changes in CVS. Any idea on the timeframe for >the next release? > >-----Original Message----- >From: qui...@li... >[mailto:qui...@li...] On Behalf Of >Oren Miller >Sent: Thursday, January 26, 2006 5:51 PM >To: Jain, Anil >Cc: qui...@li... >Subject: Re: [Quickfix-developers] RE: In-Session Logon to Reset >SequenceNumber > >QuickFIX Documentation: >http://www.quickfixengine.org/quickfix/doc/html/index.html >QuickFIX Support: http://www.quickfixengine.org/services.html > >Anil, > >There is a fix for this that will be going out with the next release (or >in CVS if you are adventurous). Please try it again at that time and >let us know if it works correctly. > >--oren > >Jain, Anil wrote: > > > >>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, and 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 >>conformation!) >> >>So, after request has been made, and before a response to it has been >>received, the QuickFIX engine immediately processes the exchange's >>earlier /test request/ by sending a heartbeat and increases the >>exchange sequence number to 2 *(:`(*. The fact is that the test >>request was made under previous logon regime, with different sequence >>number. And the sequence number being incremented 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 number of 1. >> >>This is just a small crib to a great product! I resolved it by >>suspending reset logon in this case till a heartbeat has been received >> >> > > > >>in fromAdmin. >> >>Thanks. >> >>Anil Jain >> >> >> >> >> >> >> >>_______________________________________________________________________ >> >>This E-Mail (including any attachments) may contain privileged or >> >> >confidential information. It is intended only for the addressee(s) >indicated above. > > >>The sender does not waive any of its rights, privileges or other >> >> >protections respecting this information. > > >>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 prohibited. > > >>If you received this E-Mail in error, please delete it and advise the >> >> >sender (by return E-Mail or otherwise) immediately. > > >>This E-Mail (including any attachments) has been scanned for viruses. >>It is believed to be free of any virus or other defect that might >> >> >affect any computer system into which it is received and opened. > > >>However, it is the responsibility of the recipient to ensure that it is >> >> >virus free. > > >>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. > > >>Such communications are retained and may be produced to regulatory >> >> >authorities or others with legal rights to the information. > > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log >files for problems? Stop! Download the new AJAX search engine that >makes searching your log files as easy as surfing the web. DOWNLOAD >SPLUNK! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 >_______________________________________________ >Quickfix-developers mailing list >Qui...@li... >https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 >_______________________________________________ >Quickfix-developers mailing list >Qui...@li... >https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > > > |
|
From: Oren M. <or...@qu...> - 2006-01-26 23:19:31
|
Anil, There is a fix for this that will be going out with the next release (or in CVS if you are adventurous). Please try it again at that time and let us know if it works correctly. --oren Jain, Anil wrote: > 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, and 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 > conformation!) > > So, after request has been made, and before a response to it has been > received, the QuickFIX engine immediately processes the exchange's > earlier /test request/ by sending a heartbeat and increases the > exchange sequence number to 2 *(:`(*. The fact is that the test > request was made under previous logon regime, with different sequence > number. And the sequence number being incremented 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 number of 1. > > This is just a small crib to a great product! I resolved it > by suspending reset logon in this case till a heartbeat has been > received in fromAdmin. > > Thanks. > > Anil Jain > > > > > > > >_______________________________________________________________________ > >This E-Mail (including any attachments) may contain privileged or confidential information. It is intended only for the addressee(s) indicated above. >The sender does not waive any of its rights, privileges or other protections respecting this information. >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 prohibited. >If you received this E-Mail in error, please delete it and advise the sender (by return E-Mail or otherwise) immediately. > >This E-Mail (including any attachments) has been scanned for viruses. >It is believed to be free of any virus or other defect that might affect any computer system into which it is received and opened. >However, it is the responsibility of the recipient to ensure that it is virus free. >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. >Such communications are retained and may be produced to regulatory authorities or others with legal rights to the information. > |
