[QFJ-624] Invalid "Timed out waiting for heartbeat" and disconnect Created: 27/Jul/11  Updated: 04/Nov/16  Resolved: 19/Dec/13

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

Type: Bug Priority: Major
Reporter: Siva Ram Assignee: Unassigned
Resolution: Incomplete Votes: 3
Labels: QuickfixJ, TestRequest, timeout
Environment:

G6 machine, OS - RHL 5.4, Java version - 1.6.0_24


Issue Links:
Duplicate
is duplicated by QFJ-668 Disconnecting: Timed out waiting for ... Closed
is duplicated by QFJ-759 "Timed out waiting for heartbeat" aft... Closed

 Description   

We have the Quickfix engine operating in Acceptor mode. We frequently see scenarios where we disconnect the clients because we "Timed out waiting for heartbeat". But I am able to confirm from the network packet capture that the client heartbeats as expected and in fact promptly responds back to the test request (which was sent before the disconnect) with a heartbeat. I did search for this online and noticed a few forums were this scenario is being discussed, but no resolutions. We have seen similar scenarios in other applications when we don't set a proper socket read timeout and I am wondering if it is the same case here.



 Comments   
Comment by Grant Birchmeier [ 27/Jul/11 ]

Have you tried posting your problem to the mailing list? That should be your first stop before submitting a bug here.
http://quickfixj.org/support/

Apologies if you did that already.

Comment by Siva Ram [ 28/Jul/11 ]

No, I didn't post it on the mailing list. Will do that.

Comment by Christoph John [ 15/Feb/12 ]

Did you manage to reproduce this reliably with a current QF/J version? Can you supply a test case?
Thanks in advance,
Chris.

Generated at Sat Nov 23 07:37:24 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.