[Quickfix-developers] Re: monitor the FIX connection failure programmatically?

[Alvin W. <AW...@FF...>]

Oren, thanks!
So does it mean even when the physics connection is down and we did not 
receive logout msg, onLogout will still be invoked? If so, how can we tell 
if it is an abnormal logout/disconnection?

Not trying to argue, but what if the FIX session is not never setup from 
beginning due to network problem? Will onLogout be called?

Thanks
Alvin






"Oren Miller" <or...@qu...>
11/04/2005 09:38 AM

 
        To:     <qui...@li...>, 
<qui...@li...>, "Alvin Wang" 
<AW...@FF...>
        cc: 
        bcc: 
        Subject:        Re: monitor the FIX connection failure programmatically?


The onLogout callback would tell you anytime a sessions connection is 
lost.
 
--oren
----- Original Message ----- 
From: Alvin Wang 
To: qui...@li... ; qui...@li... ; Oren Miller 
Sent: Friday, November 04, 2005 1:40 PM
Subject: monitor the FIX connection failure programmatically?


Hi, 

How can I monitor the FIX connection failure? I know I can tell from 
quickfix event log. But is there a way that my code can be notified 
programmatically such as "onEvent()"? The problem we are experiencing is 
that we did not know the connection was down in production for 2 hours 
until a trader tried to send an order via FIX. 

many thanks! 
Alvin ********************************************************************** 
This e-mail message is intended solely for the use of the addressee. The 
message may contain information that is privileged and confidential. 
Disclosure to anyone other than the intended recipient is prohibited. If 
you are not the intended recipient, please do not disseminate, distribute 
or copy this communication, by e-mail or otherwise. Instead, please notify 
us immediately by return e-mail (including the original message with your 
reply) and then delete and discard all copies of the message. We have 
taken precautions to minimize the risk of transmitting software viruses 
but nevertheless advise you to carry out your own virus checks on any 
attachment to this message. We accept no liability for any loss or damage 
caused by software viruses. 
**********************************************************************