Re: [Quickfixj-users] Logout sent at session start

[Pergus <per...@gm...>]

Chris, thanks for your reply. Unfortunately, my problem occurs when the
session is automatically recycling at the end of the day (I am using a daily
session schedule). I am not controlling the logout and disconnect with my
application code in that case.

On 3/6/07, Chris Hurst <chr...@ho...> wrote:
>
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
>  Unitl someone gives you a far better answer, but just pointing out the
> obvious ...
>
> Your initiator isn't using stop(true) is i.e. force disconnect  rather
> than stop(false) or just stop ()
> (Ref : quickfix.Connector.java) , I think thats part of ypour application
> code and not a setting ??obviously depending on which stop is selected
> you'll get your intended and unintended behaviour as regards waiting for the
> logout.
>
> ------------------------------
> From:  *Pergus <per...@gm...>*
> Reply-To:  *qui...@li...*
> To:  *qui...@li...*
> Subject:  *[Quickfixj-users] Logout sent at session start*
> Date:  *Tue, 6 Mar 2007 14:05:11 +0100*
> >QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> >QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
> Hi,
>
>  I am running a QuickFIX/J initiator using FIX 4.2. When a session expires
> on my side (because EndTime is reached) a logout message is sent to the
> counterparty and the initiator immediately disconnects, without waiting for
> a logout response (isn't the engine supposed to wait for a logout response
> before disconnecting according to the FIX specs?). Later on, when time
> reaches StartTime for the new session, the first thing that happens is that
> the initiator sends a logout message to the counterparty and then
> disconnects. This doesn't seem right. Could anyone please explain why this
> happens? It would appear as though the engine has queued the logout response
> from the counterparty before the previous session was shut down and the
> initiator interprets it as a new message at the start of the new session.
> This becomes a problem when the counterparty doesn't ignore messages that
> are sent before logon messages have been exchanged and the sequence numbers
> get out of sync.
>
>  Many thanks,
>
>  Pergus
>
> >-------------------------------------------------------------------------
> >Take Surveys. Earn Cash. Influence the Future of IT
> >Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> >opinions on IT & business topics through brief surveys-and earn cash
> >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> >_______________________________________________
> >Quickfixj-users mailing list
> >Qui...@li...
> >https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>
>
> ------------------------------
> Upload 500 photos a month & blog with your Messenger buddies on Windows
> Live Spaces. Get yours now, FREE!<http://g.msn.com/8HMAENUK/2755??PS=47575>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Quickfixj-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>
>