[Quickfix-developers] QuickFix FailOver/Farming Support.

[pc r. <pc....@ta...>]

Hi, 
   
  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.  
   
  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. 
   
  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.  
   
  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...