[QFJ-253] CLONE -First login attempt of initiator afterStartTime is responded with logout Created: 01/Oct/07  Updated: 01/Feb/08  Resolved: 01/Feb/08

Status: Closed
Project: QuickFIX/J
Component/s: Engine
Affects Version/s: 1.2.1
Fix Version/s: None

Type: Other Priority: Default
Reporter: Michael Briganti Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

2003


 Description   

Hi Steve, it's been quite a while.
We are experiencing the bug detailed below.
Do you have a specific patch for this for 1.2.1, or is 1.3.0 stable enough
for production.

This could be related to a open bug about the timer events not being
processed in an acceptor while it's disconnected (QFJ-218). This would
cause the logout with the old sequence number to be sent the first time
someone connects. Subsequent connections should be ok and should use the
new session's sequence numbers. If we can complete the 1.3 release soon,
I'll have the fix in there. Otherwise, I'll patch 1.2.1 and release a
new version of that branch.

A temporary workaround is to call reset manually on the message
store before the new session start time.

Regards,

Steve



 Comments   
Comment by Michael Briganti [ 01/Oct/07 ]

Hi Steve. We tried with version 1.3.0 and it appears this issue has not been fixed.

Comment by Steve Bate [ 01/Oct/07 ]

This is apparently a different issue. Does the logout message have a text field in it? If so, what does it say? I assume you've looked in the log files to see if there is anything interesting there.

Comment by Davide Tedesco [ 21/Jan/08 ]

Hi,

I got the same problem and I tried either ver. 1.3.0 and 1.3.1; they seems to carry the same bug.
I see that on EndTime the Initiator sends the logout and disconnect, without waiting for the ack from the Acceptor.
As a workaround I tried to set LogoutTimeOut = 10 sec, but the Initiator drop the connection at EndTime, without waiting 10 sec.
As a consequence at next StartTime the Initiator sends a logout first, problably because it didn't receive the ack to the logout at the last Endtime.
So the 2 bugs seems to be realated.

Regards,

Davide

Generated at Sun May 19 11:20:53 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.