Re: [Quickfix-users] Incorrect Data Format aka possDupFlag issue

[aupadras <ani...@ya...>]

Hi,

I contacted my counter-party to match my msg type '8' data dictionary
settings.., so hopefully I will not reject their messages. I assume this
will fix the problem.

I am using following piece of code and worried that initiator.stop() is
initiating the log -out. I have StartTime=00:01:00 and EndTime=23:55:00 in
the config file. How can my application continuously communicate with my
counter-party without logging out i..,e Do I need to delete initiator.stop
or is there any safe mechanism to handle this like initiator to be stopped
when clock Time == EndTime? Or Am I completely out of whack.

        initiator.start();  					
	application.run();						
        initiator.stop();		 
        return 0;	

In addition to the above, sometimes I under-go fatal problems like... socket
initiator error,resend request issues and msgseqno mis-match (msg seq no is
too low or too high) etc.., with my counter-party. In those cases, I am
asking my counter-party to reset the seqno. However, once we go live and
real time this is not the best option. Please suggest the best ways to
design the robust system.

My Config settings are :
ResetOnDisconnect=N
CheckLatency=N
ResetOnLogon=N
ResetOnLogout=N
SendResetSeqNumFlag=N
RefreshOnLogon=Y
PersistMessages=Y
MillisecondsInTimeStamp=Y
UseDataDictionary=Y

Also, I am implementing try-catch mechanism in setting and getting the field
information defined in data-dictionary. 

Finally, I don't recall of seeing the print statement outputs in onMessage
or fromAPP block. I do see some action from toAPP (when message is sent to
target), but never seen from fromAPP or onMessages. Do I need to call
fromAPP and onMessages(Execution Reports) in my application whereas toAPP is
called by default by QF when message is being sent to target ???

Please Advise.

Thanks,
aupadras.



--
View this message in context: http://quickfix.13857.n7.nabble.com/Incorrect-Data-Format-aka-possDupFlag-issue-tp6518p6520.html
Sent from the QuickFIX - User mailing list archive at Nabble.com.