Re: [Quickfixj-users] Quickfixj client disconnecting immediately after sending logout instead of waiting for logout response?

[Ajay P. <ap...@en...>]

No Ari
You are right, I have reported this before. We are still using 1.6 and we
have this problem where we ended up missing an execution report sent a ms
after our logout was sent. The workaround suggested at the time was to
adjust your session end time to slightly later so that you rather rely on
the other side to send the logout from your side (ie if you are talking
about a timed logout)
I was not able to open a jira at the time, but I dont think there is any
configuration you can change on your end other than the timing workaround.

Ajay Patwardhan


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
>