Re: [Quickfix-developers] Connecting/disconnecting fails

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

Version?
  ----- Original Message -----=20
  From: Francis Gingras=20
  To: qui...@li...=20
  Sent: Tuesday, July 05, 2005 8:40 PM
  Subject: [Quickfix-developers] Connecting/disconnecting fails


  I am having a problem when connecting/disconnecting.  The 3rd logon =
always fails and the sequence numbers are not reset.

  This is the log from a ThreadedInitiator running the latest sources.

  Outgoing:
  =
8=3DFIX.4.2=019=3D85=0135=3DA=0134=3D1=0149=3DFIXUSER=0152=3D20050706-00:=
16:38.828=0156=3DORDERS=0196=3DFIXPASS=0198=3D0=01108=3D30=01141=3DY=0110=
=3D246=01
  =
8=3DFIX.4.2=019=3D56=0135=3D5=0134=3D2=0149=3DFIXUSER=0152=3D20050706-00:=
16:46.703=0156=3DORDERS=0110=3D207=01
  =
8=3DFIX.4.2=019=3D85=0135=3DA=0134=3D1=0149=3DFIXUSER=0152=3D20050706-00:=
16:50.968=0156=3DORDERS=0196=3DFIXPASS=0198=3D0=01108=3D30=01141=3DY=0110=
=3D245=01
  =
8=3DFIX.4.2=019=3D56=0135=3D5=0134=3D2=0149=3DFIXUSER=0152=3D20050706-00:=
17:00.578=0156=3DORDERS=0110=3D208=01
  =
8=3DFIX.4.2=019=3D85=0135=3DA=0134=3D3=0149=3DFIXUSER=0152=3D20050706-00:=
17:05.093=0156=3DORDERS=0196=3DFIXPASS=0198=3D0=01108=3D30=01141=3DY=0110=
=3D237=01
  =
8=3DFIX.4.2=019=3D105=0135=3D5=0134=3D4=0149=3DFIXUSER=0152=3D20050706-00=
:17:05.109=0156=3DORDERS=0158=3DMsgSeqNum too low, expecting 2 but =
received 1=0110=3D143=01

  Incoming:
  =
8=3DFIX.4.2=019=3D00074=0135=3DA=0149=3DORDERS=0156=3DFIXUSER=0134=3D1=01=
52=3D20050706-00:16:38.921=01108=3D30=01141=3DY=0198=3D0=0110=3D179=01
  =
8=3DFIX.4.2=019=3D00074=0135=3DA=0149=3DORDERS=0156=3DFIXUSER=0134=3D1=01=
52=3D20050706-00:16:50.968=01108=3D30=01141=3DY=0198=3D0=0110=3D184=01
  =
8=3DFIX.4.2=019=3D00074=0135=3DA=0149=3DORDERS=0156=3DFIXUSER=0134=3D1=01=
52=3D20050706-00:17:05.109=01108=3D30=01141=3DY=0198=3D0=0110=3D172=01

  Events:
  20050706-00:16:38 : Created session
  20050706-00:16:38 : Connecting to 127.0.0.1 on port 10501
  20050706-00:16:38 : Connection succeeded
  20050706-00:16:38 : Initiated logon request
  20050706-00:16:38 : Logon contains ResetSeqNumFlag=3DY, reseting =
sequence numbers to 1
  20050706-00:16:38 : Received logon response
  20050706-00:16:46 : Initiated logout request
  20050706-00:16:46 : Socket Error: Connection reset by peer.
  20050706-00:16:46 : Disconnecting
  20050706-00:16:50 : Created session
  20050706-00:16:50 : Connecting to 127.0.0.1 on port 10501
  20050706-00:16:50 : Connection succeeded
  20050706-00:16:50 : Initiated logon request
  20050706-00:16:50 : Logon contains ResetSeqNumFlag=3DY, reseting =
sequence numbers to 1
  20050706-00:16:50 : Received logon response
  20050706-00:17:00 : Initiated logout request
  20050706-00:17:00 : Socket Error: Connection reset by peer.
  20050706-00:17:00 : Disconnecting
  20050706-00:17:04 : Created session
  20050706-00:17:05 : Connecting to 127.0.0.1 on port 10501
  20050706-00:17:05 : Connection succeeded
  20050706-00:17:05 : Initiated logon request
  20050706-00:17:05 : Logon contains ResetSeqNumFlag=3DY, reseting =
sequence numbers to 1
  20050706-00:17:05 : MsgSeqNum too low, expecting 2 but received 1
  20050706-00:17:05 : Disconnecting
  20050706-00:17:05 : Socket Error
  20050706-00:17:05 : Initiated logon request

  I'm not reporting this as a bug because I'm not sure if this happening =
because the server is sending MsgSeqNum =3D 1 after the logon request.

  1) Since all the server messages are the same, why is QF throwing a =
MsgSeqNum too low only on the third login?
  2) Why isn't QF resetting the MsgSeqNums after the second logoff?
  3) Both ResetOnLogout and ResetOnDisconnect and enabled.  If I disable =
them, I get this error on the second login.
  4) The code calls socket.stop() to disconnect and a new socket is =
instantiated before every socket.start().

  Thanks,

  Francis