|
From: Grant B. <gbi...@co...> - 2020-06-22 22:19:37
|
Answers in order: * Yes, you are correct. * Yes, your app should wait. * Don't know if there's something wrong with your setup, because we don't know anything about your setup. * Upgrading might help, if this is due to some old bug that was fixed long ago. In fact, I'd say that's a strong possibility, because 1.3 is not just old, it's *very* old. It's 12 years old! Or there's an outside chance that your counterparty is misbehaving. Is it possible that they're killing the connection as soon as they receive your logout instead of sending a logout back? I'm not saying this is likely (though I have seen some counterparties do dumb stuff), but it's not impossible. -Grant On Mon, Jun 22, 2020 at 4:20 PM Aaron (Ari) Engel <ar...@pi...> wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J <http://www.quickfixj.org/documentation/QuickFIX/J> Support: > http://www.quickfixj.org/support/ > > > Hi, I am seeing that my quickfixj client disconnects immediately after > sending a logout request (35=5) to the server, but I believe FIX protocol > states that it should wait for the logout response (35=5) from the server > before disconnecting. Is that correct? Should it be waiting? Is there > something wrong with my setup that is causing this? Note I am using an old > version of quickfixj (1.3.X) but I dont know if that impacts this. Any > guidance? Thanks! > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > -- Grant Birchmeier *Connamara Systems, LLC* *Made-To-Measure Trading Solutions.* Exactly what you need. No more. No less. http://connamara.com -- This email, along with any attachments, is confidential. If you believe you received this message in error, please contact the sender immediately and delete all copies of the message. Thank you from Connamara Systems, LLC. |