Re: [Quickfix-developers] QuickFix FailOver/Farming Support.

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

To do this we would need some sort of revert method on the MessageStore =
interface which would revert to the persisted state.  This could then be =
called by a session when receiving a logon.  It actually might be a =
useful thing to do in all logon situations.  It also gives us the =
ability to modify sequence numbers and such without having to restart =
the engine.

--oren
  ----- Original Message -----=20
  From: pc redev=20
  To: qui...@li...=20
  Sent: Thursday, May 25, 2006 2:08 PM
  Subject: [Quickfix-developers] QuickFix FailOver/Farming Support.


  Hi,=20

  I have a QuickFixEngine connected to a "Clustered" MS SQL Server =
backend, running fine.  I would like to be-able to provider =
"FailOver/Farming" support like:

  Primary Machine:  Fix Engine Running Serving Active Clients
  Secondary Machine: Fix Engine Running in No client connections.

  Both Fix Engines are connected to the clustered SQL Server for the =
message store. =20

  If I "pull the plug" on A, clients are disconnected and connect to =
"secondary", which in theory when they connect we pick up the session =
from where it left off.

  The problem is the "Secondary" quick fix engine does not know to =
"re-read" the clients "Sessions" when they connect, it appears that this =
is performed when the "Fix Engine Starts Up" probably during the create =
session.

  My only solution at the moment would be to have the "Secondary" fix =
engine start on failover, i.e cold standby, which is not ideal.=20

  In the Fix Engine logic is it possible to "detect" a client socket =
connect and force a "re-read" of session information from the message =
store  cleanly with no side effects?   I'd prefer not to change the Fix =
engine source code. =20

  Any info would be appreciated.

  Regards

  Phil.


-------------------------------------------------------------------------=
-----
  Copy addresses and emails from any email account to Yahoo! Mail - =
quick, easy and free. Do it now...