quickfix-developers

[Quickfix-developers] multiple connections break

[H. S. <st...@un...>]

hi guys,

I just encountered an interesting thing with quickfix which is not on FIX protocol layer but TCP. 
we configured 3 counterparts in our settings file and quickfix tries to connect to them. if one of those counterparts filters and drops the TCP connection (no RST in reply to our SYN), quickfix is waiting and the other connections either dont get established or go down with "waiting for heartbeat message".

i was yet not looking into the quickfix code but i assume its a problem with the engine not trying to set up connections in parallel - or maybe not having any timeout for opening net connections.


the problem with that is that counterparts can bring down other FIX connections by just ignoring SYN packets from us.

did one of you guys ever see any similar problem? 

regards,
heri


p.s.: this is quickfix 1.9.2 on FreeBSD 5.3. Im just installing 1.9.4 for testing.



-- 
This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.

Re: [Quickfix-developers] multiple connections break

[Joerg T. <Joe...@ma...>]

Hi Heri,

> I just encountered an interesting thing with quickfix which is not on FIX protocol
> layer but TCP. we configured 3 counterparts in our settings file and quickfix tries to
> connect to them. if one of those counterparts filters and drops the TCP connection (no
> RST in reply to our SYN), quickfix is waiting and the other connections either dont get
> established or go down with "waiting for heartbeat message".
> 
> i was yet not looking into the quickfix code but i assume its a problem with the engine
> not trying to set up connections in parallel - or maybe not having any timeout for
> opening net connections.

Actually this depends on which Initiator you use: if you use the ThreadedSocketInitiator, 
every connection is setup in parallel in a separate thread: See the method doConnect()
in src/C++/ThreadedSocketInitiator.cpp. If you just use SocketInitiator, the method 
doConnect() does the connection setup one by one.

So if you currently use SocketInitiator, please replace it by the threaded version and 
give it another try.

If you are already using ThreadedSocketInitiator, then there may be another problem.

Anyway, I would give 1.9.4 a try.

Cheers, Jörg

-- 
Joerg Thoennes
                                http://macd.com
Tel.: +49 (0)241 44597-24      Macdonald Associates GmbH
Fax : +49 (0)241 44597-10      Lothringer Str. 52, D-52070 Aachen