|
From: Daniel C. <da...@bl...> - 2018-11-30 18:37:07
|
Hi,
I think this is an old issue, but still seems to be a problem with the
latest version of quickfixj 2.1.0.
After my initiator sends a Logon message, the acceptor immediately sends
back a Logout Message followed by closing the connection. Looking at the
tcpdump, it is clear why the connection is closed
x.x.x.x.56988 > x.x.x.x.25265: Flags [P.], cksum 0x9863 (incorrect ->
0xe431), seq 1:104, ack 1, win 21, length 103
E.....@
.@..t..........b.(.7.>..+P....c..8=FIX.4.2.9=81.35=A.34=1161.49=XXX.52=20181130-15:08:36.259.56=***.98=0.108=10.554=***.10=026.
15:08:36.336321 IP (tos 0x60, ttl 48, id 0, offset 0, flags [DF], proto TCP
(6), length 188)
x.x.x.x.x > x.x.x.x.56988: Flags [P.], cksum 0xdd5d (correct), seq
1:149, ack 104, win 4096, length 148
E`....@.0...........b...>..+(.8YP....]..*8=FIX.4.2.9=0124.35=5.34=552397.49=XXX.52=20181130-15:08:36.298.56=XXX.789=469881.58=MsgSeqNum
too low, expecting 469881 but received 1161.10=079*.
The problem is that *fromAdmin* is *never* called before *onLogout* because
of the connection reset following the logout message. I really need to
access this logout message for a couple of internal reasons.
Is there any workaround for this issue available?
Thanks
Daniel Cullender
|