Re: [Quickfix-developers] Quickfix-developers Digest, Vol 2, Issue 12

[<li...@ho...>]

thank you, I will test the logout in the way you have sent to me.

Lidia


>From: qui...@li...
>Reply-To: qui...@li...
>To: qui...@li...
>Subject: Quickfix-developers Digest, Vol 2, Issue 12
>Date: Fri, 14 Jul 2006 12:13:37 -0700
>
>Send Quickfix-developers mailing list submissions to
>	qui...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>or, via email, send a message with subject or body 'help' to
>	qui...@li...
>
>You can reach the person managing the list at
>	qui...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Quickfix-developers digest..."
>
>
>QuickFIX Documentation: 
>http://www.quickfixengine.org/quickfix/doc/html/index.html
>QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
>QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
>
>Today's Topics:
>
>    1. Message sequence number greater than expected (Lidia L?pez Cuesta)
>    2. Re: Message sequence number greater than	expected (Dave Linaker)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 14 Jul 2006 12:13:04 +0200
>From: Lidia L?pez Cuesta <li...@ho...>
>Subject: [Quickfix-developers] Message sequence number greater than
>	expected
>To: qui...@li...
>Message-ID: <BAY...@ph...>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Hi all,
>
>I have a client application using a SocketInitiator. This application only
>sends the logon a datamarketrequest and when the application is closed a
>logout is sent. But is seems that when the socketinitiatior is disposed a
>logout message is sent automatically (34=5).
>
>When I open the application again, a resend message is received asking for
>the second logout (7=5), then the application resend this message
>automatically with 34=5 again and then the message 34=7, I don't know why
>the 34=6(logon message) is not resend. When receive the 34=7 fails because
>meff is expecting 34=6.
>
>I have 2 questions:
>1. Anyone knows why is send a logout when the socket is closed? the problem
>is that if the socket is closed MEFF can't send its confirmation and I
>supposed that this is the reason why ask for the resend
>2. Why when the resend is asked, the logon message(34=6) is not resend?
>
>I have attached the messages.log.
>
>Lidia.
>
>-------------- next part --------------
>A non-text attachment was scrubbed...
>Name: FIX.4.4-A880-MEFF.messages.log
>Type: application/octet-stream
>Size: 3676 bytes
>Desc: not available
>Url : 
>http://sourceforge.net/mailarchive/forum.php?forum=quickfix-developers/attachments/20060714/e28de860/attachment.obj
>
>------------------------------
>
>Message: 2
>Date: Fri, 14 Jul 2006 15:58:20 +0100
>From: "Dave Linaker" <dav...@ma...>
>Subject: Re: [Quickfix-developers] Message sequence number greater
>	than	expected
>To: <qui...@li...>
>Message-ID: <003301c6a755$f21b1e00$0800000a@macdLaptop>
>Content-Type: text/plain;	charset="us-ascii"
>
> > I have a client application using a SocketInitiator. This
> > application only sends the logon a datamarketrequest and when
> > the application is closed a logout is sent. But is seems that
> > when the socketinitiatior is disposed a logout message is sent
> > automatically (34=5).
> >
>
>How are you sending the Logout? Are you calling Logout, e.g.:
>
>QuickFix.Session.lookupSession(sessionID).logout();
>
>You can also just stop the initiator and it will automatically complete
>the logout before disconnecting.
>
>If you send a logout using sendToTarget() then quickfix won't be aware
>that it has initiated the logout, so when it receives the Logout
>response it treats it like a logout request and responds with a Logout,
>but the otherside will have disconnected before it receives this
>additional logout message, hence the resend behaviour. Avoid doing this.
>
> > When I open the application again, a resend message is
> > received asking for the second logout (7=5), then the
> > application resend this message automatically with 34=5 again
> > and then the message 34=7, I don't know why the
> > 34=6(logon message) is not resend. When receive the 34=7
> > fails because meff is expecting 34=6.
> >
>
>The resend behaviour looks ok to me. First you get a resend request
>asking for messages from SeqNum 5 onwards (i.e. 7=5 and 16=0):
>
>8=FIX.4.4
9=70
35=2
34=14
52=20060714-10:06:53
49=MEFF
50=M3
56=A880
57=
>351
7=5
16=0
10=034

>
>Your engine responds by sending a gapfill message with SeqNum 5 (i.e.
>34=5) saying the next expected SeqNum should be 7 (i.e. 36=7):
>
>8=FIX.4.4
9=106
35=4
34=5
43=Y
49=A880
50=351
52=20060714-10:03:25.250
5
>6=MEFF
57=M3
122=20060714-10:03:25.250
36=7
123=Y
10=103

>
>...and the next message sent is with SeqNum 7 (i.e. 34=7):
>
>8=FIX.4.4
9=174
35=V
34=7
43=Y
49=A880
50=351
52=20060714-10:03:24.609
5
>6=MEFF
57=M3
122=20060714-10:03:22.906
22=8
48=21
55=[N/A]
146=1
262=000
>0001
263=1
264=0
265=0
267=1
269=6
461=FXXXSX
10=221

>
>Basically a SequenceReset message was sent in place of messages 5 and 6,
>which is correct because these messages were originally a logout and a
>logon and should not be resent.
>
>I don't really see why the counterparty ended the session.
>
>cheers
>Dave
>
>
>
>
>
>------------------------------
>
>
>-------------------------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job 
>easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
>
>------------------------------
>
>_______________________________________________
>Quickfix-developers mailing list
>Qui...@li...
>https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>
>End of Quickfix-developers Digest, Vol 2, Issue 12
>**************************************************