Re: [Quickfix-developers] [qfj] connect and logon in wrong order after disconnect?

[VP M. IT A. E. T. <ass...@gm...>]

Hi

This is the same problem as I had reported two days ago.

Once a disconnect occurs the Session is not in a valid state to do a logon.
So a session must be created. According to Oren, in Quickfix classic
the latest version fixes this.

I am not sure how far along the qfj version is.

I am also trying to solve this problem with a counter party.


On 8/25/05, Graham Miller <gm...@de...> wrote:
>=20
>=20
>=20
> I was going through the certification process with Archipelago using qfj.=
  I
> have managed to pass all the tests except the last one, which requires th=
at
> your engine recover gracefully from an unexpected disconnect.  It appears
> that perhaps after an unexpected disconnect, my engine is trying to send =
a
> logon message before the socket is reconnected.  At least that's what the
> log would indicate:
>=20
> 17:00:57,414 DEBUG SocketInitiator:350 - connection closed:
> net.gleamynode.netty2.Session@1c9a690
> 17:00:57,415 DEBUG SocketInitiator:353 - unsolicited disconnect
> <20050825-21:00:57, FIX.4.1:DMAM->ARCA, event> (Disconnecting)
> 17:00:57,415 DEBUG SocketInitiator:425 - responder: disconnect
> <20050825-21:00:58, FIX.4.1:DMAM->ARCA, event> (Initiated logon request)
> 17:00:58,030 DEBUG SocketInitiator:336 - connection established:
> net.gleamynode.netty2.Session@1c9a690
>=20
> I used Ethereal to verify that the logon request was not being sent acros=
s
> the wire.  Because the certification server never receives the logon
> request, it eventually times out.
>=20
> I looked through the code a little bit and it seems like there is no
> mechanism to ensure that the logon is after the socket reconnect, but I'm
> pretty unfamiliar with it, so I wouldn't be surprised if I'm missing
> something.
>=20
> I am using qfj beta 1, and have seen this behavior on both a windows and =
a
> linux machine.
>=20
> Thanks for any help.
>=20
> graham
>