Re: [Quickfix-developers] Logout reason

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

Well, this isn't really a serious error condition that requires any 
intervention on your part.  If the sequence number is too high, QuickFIX 
should just send out a resend request and recover the missing messages. 
There shouldn't even be a reject message because it isn't a reject 
scenarion.  I certainly don't think you need to be incrementing sequence 
numbers.  Are you sure that a resend request isn't going out?  Do you have 
more complete logs?

--oren

----- Original Message ----- 
From: "Francis Gingras" <fr...@at...>
To: <qui...@li...>
Sent: Monday, June 13, 2005 3:47 PM
Subject: [Quickfix-developers] Logout reason


> 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
>
> Here's another question on an old favorite: finding the elusive logout (or
> failed login) reason.
>
> Scenario using QF from C# with the latest files from CVS.  RequestNums are
> set to 1,1, and the server is cycled only once a week.
>
> QF initiator send a Logon request:
> 8=FIX.4.2
9=75
35=A
34=1
49=USER
52=20050613-20:26:19.281
56=TEST
96=passwor
> d
98=0
108=30
10=136

>
> and server responds with:
> 8=FIX.4.2
9=00065
35=A
49=TEST
56=USER
34=481
52=20050613-20:26:19.312
108=3
> 0
98=0
10=180

>
> Now QF rejects the message and logs "MsgSeqNum too high, expecting 1 but
> received 481" in the event log.
>
> Question: how can I get this reject reason in fromAdmin? The client does 
> not
> 'see' this rejection message so it has no idea why the login didn't work.
>
> I added this to Session::validLogonState.  This should (I think) send the
> logout reason to fromAdmin, but it doesn't.
>
>  if ( msgType == MsgType_Logout )
>    return true;
>
> Then I tried implementing the QuickFix.Log interface and added
> public void onEvent(string @string)
> {  log everything here }
> but this method is never triggered.
>
> I looked for onError but it doesn't seem to be available from C#.
>
> What is the best way to work around this?  Arbitrarily incrementing
> setNextTargetMsgSeqNum() until the login is successful is clumsy at best.
>
> Thanks,
>
> Francis Gingras
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you 
> shotput
> a projector? How fast can you ride your desk chair down the office luge 
> track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>