{{Quickfixn}} Session does not reconnect
Francis Gingras
francis at tradeintegration.com
Tue Feb 23 08:20:26 PST 2016
Hi Rob,
I should have posted the QF log, but all it contains is a login attempt with 141=Y. The CompIDs are not the issue--they haven't changed in years--and the connection is fine if I shut down QF and restart the app. That counterparty's behavior of dropping the connection after a valid login attempt is new, but I think it is not handled correctly by QF.
I will have to launch a timer to monitor QF to make sure it tries to reconnect and if not, stop/start the socket again manually.
Is that normal?
Thanks,
Francis
__________________________________
Monday, February 22, 2016, 12:23:14 PM, Rob wrote:
Hello Francis ,
Quick answer -
I would check to make sure SenderCompID and TargetCompIDs line up.
And also it is possible that your outbound sequence number is too low - example : you're sending 34=1 but
they are expecting higher.
Both of those scenarios, I think, could cause the FIX engine to ignore your logon request.
Rgds,
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20160223/b201be8c/attachment-0001.htm>
More information about the Quickfixn
mailing list