Logout sequence corner cases

erikvanzijst_x · May 22, 2006, 8:55am

Imported from previous forum

erikvanzijst_x · May 22, 2006, 8:55am

Sorry for crossposting, but my question didn’t attract much attention in “4.0 Session” -

After having read the specification, I’m still having some trouble properly understanding the logout sequence. Maybe someone on the list can help me out.

Consider the following situation:

I am the logout initiator and I send my Logout message. However, when the counterparty responds with his logout message, I discover that it has a seqNo too high.

What can I do now? Sending a ResendRequest will consume a new outbound sequence number, so my earlier Logout message will no longer be the last message in the connection.

On page 32, the FIX.4.4 specification says: “Note counterparty may send a ResendRequest message if Logout message response has MsgSeqNum too high and then re-initiate the Logout process.”

What does “re-initiate the Logout process” mean in this context? Does it mean that my ResendRequest invalidates my earlier Logout message and that I will have to send a new Logout message by the time the acceptor has sent the necessary GapFills?

kind regards,
Erik van Zijst

wushaoping1 · May 22, 2006, 9:27am

Sorry for crossposting, but my question didn’t attract much attention
in “4.0 Session” -

After having read the specification, I’m still having some trouble
properly understanding the logout sequence. Maybe someone on the list
can help me out.

Consider the following situation:

I am the logout initiator and I send my Logout message. However, when
the counterparty responds with his logout message, I discover that it
has a seqNo too high.

What can I do now? Sending a ResendRequest will consume a new outbound
sequence number, so my earlier Logout message will no longer be the last
message in the connection.

On page 32, the FIX.4.4 specification says: “Note counterparty may send
a ResendRequest message if Logout message response has MsgSeqNum too
high and then re-initiate the Logout process.”

What does “re-initiate the Logout process” mean in this context? Does it
mean that my ResendRequest invalidates my earlier Logout message and
that I will have to send a new Logout message by the time the acceptor
has sent the necessary GapFills?

kind regards, Erik van Zijst

Send a TestRequest message before Send Logout Message, So you can find gap from the TestRequest’s heartbeat.

erikvanzijst_x · May 22, 2006, 10:16am

Sorry for crossposting, but my question didn’t attract much
attention in “4.0 Session” -

After having read the specification, I’m still having some trouble
properly understanding the logout sequence. Maybe someone on the list
can help me out.

Consider the following situation:

I am the logout initiator and I send my Logout message. However, when
the counterparty responds with his logout message, I discover that it
has a seqNo too high.

What can I do now? Sending a ResendRequest will consume a new outbound
sequence number, so my earlier Logout message will no longer be the
last message in the connection.

On page 32, the FIX.4.4 specification says: “Note counterparty may
send a ResendRequest message if Logout message response has MsgSeqNum
too high and then re-initiate the Logout process.”

What does “re-initiate the Logout process” mean in this context? Does
it mean that my ResendRequest invalidates my earlier Logout message
and that I will have to send a new Logout message by the time the
acceptor has sent the necessary GapFills?

kind regards, Erik van Zijst

Send a TestRequest message before Send Logout Message, So you can find
gap from the TestRequest’s heartbeat.

But then what if the acceptor sends another message after it responded to the TestRequest? This post-TestRequest message could still get lost.

byroncoetzee_x · May 22, 2006, 12:59pm

Hi,

your code logic must check for missing messages always, and then retry for logout again.

Cheers
Byron

Sorry for crossposting, but my question didn’t attract much
attention in “4.0 Session” -

After having read the specification, I’m still having some trouble
properly understanding the logout sequence. Maybe someone on the
list can help me out.

Consider the following situation:

I am the logout initiator and I send my Logout message. However,
when the counterparty responds with his logout message, I discover
that it has a seqNo too high.

What can I do now? Sending a ResendRequest will consume a new
outbound sequence number, so my earlier Logout message will no
longer be the last message in the connection.

On page 32, the FIX.4.4 specification says: “Note counterparty may
send a ResendRequest message if Logout message response has
MsgSeqNum too high and then re-initiate the Logout process.”

What does “re-initiate the Logout process” mean in this context?
Does it mean that my ResendRequest invalidates my earlier Logout
message and that I will have to send a new Logout message by the
time the acceptor has sent the necessary GapFills?

kind regards, Erik van Zijst

Send a TestRequest message before Send Logout Message, So you can find
gap from the TestRequest’s heartbeat.

But then what if the acceptor sends another message after it responded
to the TestRequest? This post-TestRequest message could still get lost.

erikvanzijst_x · May 22, 2006, 1:16pm

Hi,

your code logic must check for missing messages always, and then retry
for logout again.

OK, so if I detect a sequence gap after I sent my initiating Logout message, I should send a ResendRequest, wait for all gap fills and then send a new Logout?

Cheers Byron

Sorry for crossposting, but my question didn’t attract much
attention in “4.0 Session” -

After having read the specification, I’m still having some trouble
properly understanding the logout sequence. Maybe someone on the
list can help me out.

Consider the following situation:

I am the logout initiator and I send my Logout message. However,
when the counterparty responds with his logout message, I discover
that it has a seqNo too high.

What can I do now? Sending a ResendRequest will consume a new
outbound sequence number, so my earlier Logout message will no
longer be the last message in the connection.

On page 32, the FIX.4.4 specification says: “Note counterparty may
send a ResendRequest message if Logout message response has
MsgSeqNum too high and then re-initiate the Logout process.”

What does “re-initiate the Logout process” mean in this context?
Does it mean that my ResendRequest invalidates my earlier Logout
message and that I will have to send a new Logout message by the
time the acceptor has sent the necessary GapFills?

kind regards, Erik van Zijst

Send a TestRequest message before Send Logout Message, So you can
find gap from the TestRequest’s heartbeat.

But then what if the acceptor sends another message after it
responded to the TestRequest? This post-TestRequest message could
still get lost.

parnellflynn_x · May 22, 2006, 1:49pm

Yes, ideally you would like to resolve all gap issues before logout.

Hi,

your code logic must check for missing messages always, and then retry
for logout again.

OK, so if I detect a sequence gap after I sent my initiating Logout
message, I should send a ResendRequest, wait for all gap fills and then
send a new Logout?

Cheers Byron

Sorry for crossposting, but my question didn’t attract much
attention in “4.0 Session” -

After having read the specification, I’m still having some
trouble properly understanding the logout sequence. Maybe
someone on the list can help me out.

Consider the following situation:

I am the logout initiator and I send my Logout message. However,
when the counterparty responds with his logout message, I
discover that it has a seqNo too high.

What can I do now? Sending a ResendRequest will consume a new
outbound sequence number, so my earlier Logout message will no
longer be the last message in the connection.

On page 32, the FIX.4.4 specification says: “Note counterparty
may send a ResendRequest message if Logout message response has
MsgSeqNum too high and then re-initiate the Logout process.”

What does “re-initiate the Logout process” mean in this context?
Does it mean that my ResendRequest invalidates my earlier Logout
message and that I will have to send a new Logout message by the
time the acceptor has sent the necessary GapFills?

kind regards, Erik van Zijst

Send a TestRequest message before Send Logout Message, So you can
find gap from the TestRequest’s heartbeat.

But then what if the acceptor sends another message after it
responded to the TestRequest? This post-TestRequest message could
still get lost.

Topic		Replies	Views
Gap-Fill for Logout message imported , 44-changes , xid_165503	2	83	March 27, 2012
Receiving Logout Message imported , general-qa , xid_167209	1	10	December 4, 1998
Initiation of Logout on sending Resend Request when Logout confirmation is recieved. imported , general-qa , xid_166508	1	9	February 27, 2002
Logout scenario with message gap imported , 40-session , xid_164833	3	87	May 13, 2011
Resend Request and LogOut Response imported , 40-session , xid_164739	2	8	February 20, 2002

Logout sequence corner cases

Related topics