[Quickfix-developers] ThreadedSocketInitiator eats file descriptors because of possibly open tcp sockets

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

hi oren,

i just discovered an issue with QF 1.12.4. QF does not close sockets
when connections fail. therefore it starts eating one file descriptor
per failed connection attempt. you can easily reproduce it by using the
ThreadedSocketInitiator instead of the unthreaded version in the
tradeclient example. now configure the engine to connect to an non
existing address (my peer does not return RST but simply times out as
the peer is turned off). 

for every failed connection attempt that the screenlogfactory displays
on the screen, there is one more file descriptor open when having a look
on the process (used fstat and lsof to verify).

its QF 1.12.4 on FreeBSD, maybe someone on the list can verify the
problem.



cheers,
heri