Re: [Quickfix-developers] Starting QuickFix Engine

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

You do not need to call start more than once.  After calling start,  
the engine will attempt reconnects on its own.  You can specify how  
often to attempt to reconnect using the ReconnectInterval  
configuration setting.

--oren

On Mar 14, 2006, at 8:11 AM, Nick Volpe wrote:

>
> I'm using QF 1.11.0 for Java and FIX 4.2 and have a (simple?)  
> question related to starting the QF engine.  In my code I create an  
> instance of SocketInitiator and then call the start() method to  
> start the QF engine.  I want to be able to keep trying to start the  
> engine periodically in the event that the acceptor I'm trying to  
> connect to isn't available.  What is the best way to achieve this?   
> Should I simply wrap this method call in a loop that periodically  
> calls the start() method until the isLoggedOn() method returns  
> true?  Or are there some configuration options available that I can  
> set to specify how many times to try and start the engine and the  
> period between each attempt?
>
> Thanks
> Nik  
> ********************************************************************** 
> **************************************** This email and any files  
> transmitted with it are confidential and intended solely for the  
> use of the individual or entity to whom they are addressed. Any  
> unauthorized use of the information contained in this email or its  
> attachments is prohibited. If this email is received in error,  
> please contact the sender and delete the material from your  
> computer systems. Do not use, copy, or disclose the contents of  
> this email or any attachments. Abu Dhabi Investment Authority  
> (ADIA) accepts no responsibility for the content of this email to  
> the extent that the same consists of statements and opinions made  
> which are the senders own and not made on behalf of ADIA. Nor does  
> ADIA accept any liability for any errors or omissions in the  
> content of this email caused by electronic and technical failures.  
> Although ADIA has taken reasonable precautions to ensure that no  
> viruses are present in this email, ADIA accepts no responsibility  
> for any loss or damage arising from the use of this email or its  
> attachments.  
> ********************************************************************** 
> ****************************************