Re: [Quickfix-developers] Logon contains ResetSeqNumFlag=Y, reseting sequence numbers to 1

[Oren M. <or...@qu...>]

Well, here is what the spec says on the subject:

"When using the ResetSeqNumFlag to maintain 24 hour connectivity and =20
establish a new set of sequence numbers, the process should be as =20
follows.  Both sides should agree on a reset time and the party that =20
will be the initiator of the process.  Note that the initiator of the =20=

ResetSeqNum process may be different than the initiator of the Logon =20
process. One side will initiate the process by sending a TestRequest =20
and wait for a Heartbeat in response to ensure of no sequence number =20
gaps.  Once the Heartbeat has been received, the initiator should =20
send a Logon with ResetSeqNumFlag set to Y and with MsgSeqNum of 1.  =20
The acceptor should respond with a Logon with ResetSeqNumFlag set to =20
Y and with MsgSeqNum of 1.  At this point new messages from either =20
side should continue with MsgSeqNum of 2.  It should be noted that =20
once the initiator sends the Logon with the ResetSeqNumFlag set, the =20
acceptor must obey this request and the message with the last =20
sequence number transmitted =93yesterday=94 may no longer be available.  =
=20
The connection should be shutdown and manual intervention taken if =20
this process is initiated but not followed properly."

So it would seem to me that when they send a Logon with the =20
ResetSeqNumFlag set, the first thing QF should do is send a Logon =20
message with a MsgSeqNum of 1, followed by your message with a =20
sequence number of 2.  Is this message going out?  If not then that =20
could be a problem.  I don't think we have a test case for an =20
initiator processing a ResetSeqNumFlag, so I can imagine this =20
scenario might not be handled correctly.

--oren

On Jun 30, 2005, at 9:04 AM, Alexey Zubko wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/=20
> html/index.html
> QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?=20
> QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi,
>
> I've got a new sequencing problem and I want to know who is right =20
> in this situation.
>
> In the CVS version QF reset sequence number if ResetSeqNumFlag is =20
> present in logon message.
>
> So I fail in the following scenario:
> My QF initiator connects to a third-part server (Currenex) with the =20=

> flag and receives logon
> message with sequence number 1 and with this flag too. QF (Session =20
> class) resets sequence number,
> and the next message I send has sequence number 1. So, the server =20
> sends me logout -
> "MsgSeqNum too low, expecting 2 but received 1".
>
> Who is right? Should QF reset sequence number on logon confirmation =20=

> or the server shouldn't
> send the flag, or QF reset is correct?
>
> Thank you in advance.
>
> --=20
>
> Regards,
>         Alexey Zubko
>
> Infinium Capital Corporation
> (416) 360-7000 ext. 305
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcli=
ck
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>