|
4.0 Session
< Previous Next >
Logon messages sent but not received
Richard Alfred-Jones
15 Dec 1997 6:29AM ETWhat should happen in the following scenarios:
Scenario 1:
Initiator sends Logon#x but not received by Acceptor.
Initiator is left waiting for Logon reply which is never sent.
Maybe Initiator times out after HeartBtInt and resends
Logon#x with PossDupFlag=Y. Acceptor receives the
Logon and processes it in normal way. Easy enough ?
or should the Initiator start pumping out Heartbeats and Test Requests after HeartBtInt period has gone by ?
I don't think that this would work at the Acceptor end.
but Scenario 2:
Initiator sends Logon#x and is received by Acceptor.
Acceptor sends Logon#y but not received by Initiator.
Initiator thinks "I'm logging in", Acceptor "I'm logged in".
Acceptor sends message#y+1 after some interval,
maybe heartbeat, test request or application message.
Initiator detects gap and sends ResendRequest#x+1.
Acceptor replaces Logon#x with SeqReset-GapFill#x.
The Initiator doesn't receive the Logon reply and
(the implementation I'm testing) waits forever :-(
What should the Initiator do in this case ?
Drop the connection or continue regardless ?
Logon messages sent but not received
Richard Alfred-Jones 15 Dec 1997 6:29AM ET
|
