Re: [Quickfixj-users] Explaining reconnect

[Nick F. <ni...@ox...>]

OK, it seems silly answering my own question, but for the benefit of the
archive...

I didn't look hard enough. On an abnormal disconnect a logout message is not
returned, but the method Session.disconnect() is called, which calls
onLogout() in the application and also calls
getLog().onEvent("Disconnecting"). So that gives two ways of telling. The
onLogout() message is obviously preferred.

This method (Session.disconnect()) handles the reset decisions and so on.

Nick

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of Nick
Fortescue
Sent: 19 October 2006 10:53
To: qui...@li...
Subject: [Quickfixj-users] Explaining reconnect

QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/
I've been doing some network robustness tests on my code with Quickfix/J.
Ok, if I'm honest I pulled the network cable out, then plugged it back in
again to see what would happen, and also tried killing the SSL tunnel.

The quickfix code and my app worked really well, and reconnected nicely. I
just wondered where all this magic happened, as I couldn't find the relevant
lines in the quickfix/J code.

It would be nice to know programmatically that the connection has been lost,
so I can do various things in the code, for example, alert the user. Does
this information get back to my application (say with an admin message)?

Nick



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Quickfixj-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfixj-users