[Quickfix-developers] .NET ThreadedSocketAcceptor disconnect/reconnect problems

[John H. <jh...@ca...>]

Has anybody else experienced problems with the ThreadedSocketAcceptor whereby if a session gets disconnected and subsequently tries to reconnect, the session cannot reconnect and the only solution is to stop the acceptor and restart it?  I've been having this problem intermittently since migrating up to QF 1.13.3 but can't recreate it consistently.

Recently I was able to capture the problem occurring with wireshark.  A look at the logs indicates that when this problem is happening, the acceptor is not replying to the initiator client.  Rather, the initiator is timing out on its logon attempt after five seconds.  I'm fairly certain that the acceptor isn't getting the logon attempt at the session logic level, as the incoming/outgoing sequence numbers on the acceptor side aren't incrementing with each failed attempt.

Any suggestions on what I might try to isolate the problem would be greatly appreciated.

Thanks,

   John