[Quickfix-developers] Does anyone else find that Quickfix connection management is not robust?
Brought to you by:
orenmnero
From: Peter P. <pet...@ho...> - 2009-01-09 15:21:11
|
I have three applications that want to talk to each other in a chain. Because they are three separate applications (not three DLLs in the same process), all three instances of Quickfix should be completely independent. So, I have an initiator A that connects to a hybrid (acceptor+initiator) application B, that connects to an acceptor-only application C If I start them all in quick succession on the same Windows machine (e.g. by running a batch file), B successfully connects to C, but A never manages to connect to B. I get the admin notification in A saying that it sent the Logon message, but nothing in B to say that it received it. If I start C, then pause for a few seconds, then start B, then pause for a few seconds, then start A, the logons all work properly. If I enable file logging, to see what events are being posted. Absolutely *no* events get posted when I do the batch version but the slow-and-steady version posts events and logs on. Has anyone else seen behaviour like this? Is Quickfix known to be a bit sensitive (flaky even?) when starting up? Thanks, Dan _________________________________________________________________ Imagine a life without walls. See the possibilities http://clk.atdmt.com/UKM/go/122465943/direct/01/ |