Re: [SPAM] [Quickfix-users] How to detect FIX TCP socket connection breaks

[QuickFIX <or...@qu...>]

QuickFIX won't tell you when the socket breaks/connects per se.  This=20
information is abstracted away because we try not to expose the socket=20=

layer since FIX itself does not require the use of sockets and people=20
use other transports such as RV.  What we do have are the onLogon and=20
onLogout methods inherited from the application.  onLogout will be=20
called whenever the session is broken for any reason, whether it be a=20
proper logout sequence or a socket disconnect.  When this callback is=20
invoked, you know the session has been dropped (gracefully or=20
otherwise).  I've been considering whether this method should provide=20
more detailed information about the nature of the connection loss, but=20=

so far this hasn't really been a big issue for anyone.

The onLogon method of course tells you when you have successfully=20
established a connection and logged on.  It does not tell you about=20
failed connection attempts and the like, though they are sent to the=20
logger interface.  You can also see all the attempted logon messages in=20=

the toAdmin method.

I believe for most purposes, onLogon and onLogout does the trick.

--oren

On Apr 12, 2004, at 7:23 PM, Nikhil Bose wrote:

> Hello,
> =A0
> Is there any way to detect when Quickfix 1.5 has a broken TCP socket=20=

> connection to the other FIX engine?=A0 I am using Quickfix 1.5 as an=20=

> Initiator.=A0 And I would like to know as soon as the TCP connection=20=

> with the other FIX engine is broken, and also when it reconnects.=A0=20=

> What is the easiest way to get this information.
> =A0
> Thanks,
> Sanjoy