[Quickfix-developers] Deadlock scenario: seem to be in ThreadedSocketInitiator, the stop(..) hang f
Brought to you by:
orenmnero
From: Wilhelm T. <wil...@ya...> - 2008-10-31 06:01:31
|
Hello I'm using the c# api (the bug seem to be in the cpp layer - in the initiator.stop(..) function), basically the initiator (ThreadedSocketInitiator) hang forever (may be the mutex). Here is the scenario to reproduce the bug (this scenario simulate a disconnection from a Fix Gateway and reconnect after that but the initiator hang for ever) 1) create an application and an initiator like: initiator = new ThreadedSocketInitiator(application, storeFactory, sessionSettings, logFactory, messageFactory); 2) start it: initiator.start(); 3) wait 4) unplug your network, or disable the "Local Area connection" 5) wait 6) optional step (plug back your network or enable your "Local Area connection") 7) stop initiator: initiator.stop(); // or initiator.Dispose(); same issue Does any one as an idea how to solve this issue? Thank you for your help Wilhelm |