This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
FIX connection timed-out after successful heartbeat message #795
Labels
You can continue the conversation there. Go to discussion →
I have an application that connects to a server via the FIX protocol. The dependency
QuickfixJ 2.3.0
is used. We used Oracle to save the sequence in thequickfix_sessions
table since QuickfixJ stores incoming and outgoing sequences in the database.Recently we switched from Oracle to PostgreSQL, and as a result, we began experiencing time-out problems. The TestRequest was made, and it timed out waiting for the heartbeat response. However, the response was recorded as received in the FIX messages log.
The session finally managed to log back in after the application failed to reconnect and timed out on a logon response that was being logged as received.
We occasionally observe no disconnections during the day, but occasionally they occur twice or three times. There is no consistent pattern for when it disconnects—it can happen in four hours or just one hour. However, the logs show no database issues.
The heartbeat interval is
heartbeatInt = 30s
Sample logs:
Disconnecting: Timed out waiting for logon response Initiated logon request Disconnecting: Timed out waiting for logon response
The text was updated successfully, but these errors were encountered: