[Quickfix-developers] Re: reconnecting after diconnect

[C. B. <ben...@et...>]

Oren Miller wrote:

Ok, looking at it I think the "Field not found" is an erroneous 
 message.  I bet what it really is, is the sequence number is lower than
 expected and there is no PossDupFlag (which is where the FieldNotFound 
 is coming from).  Try changing the doTargetToLow method to look like 
 this:
 
 bool Session::doTargetTooLow( const Message& msg )
 { QF_STACK_PUSH(Session::doTargetTooLow)
 
    const Header & header = msg.getHeader();
    MsgType msgType;
    PossDupFlag possDupFlag(false);
    MsgSeqNum msgSeqNum;
    header.getField( msgType );
    if( header.isSetField( possDupFlag ) )
      header.getField( possDupFlag );
    header.getField( msgSeqNum );
 
--------

I seem to have the same problem Clark Sims had some 18 days ago. BUT, my
targetCompID wants me to send a logout message instead of just dropping
the tcp connection.

would it be OK to insert a call to
   generateLogout( "Sequence number lower than expected" );

instead of the throw I now have at doTargeTooLow?