|
From: Tsz S. C. <jas...@gm...> - 2018-11-19 11:21:07
|
Hi all, We have recently found a problem that Initiator failover was stuck with the first address when acceptor compID already in use by another initiator. It seem to be related to this, though I think the change only exposed the bug, not created it. https://github.com/quickfix-j/quickfixj/commit/622b858d4a6d972b0d2006b5029f2be354d1dcdc In the case of targetCompID in use, the session was connected and active, so the address index set to one, even it was dropped afterwards. Then the initiator will try and fail forever until the session of the targetCompID is available again. How could the initiator detect the targetCompID in use and therefore could try next address in the list? Cheers Jason |