Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX connection timed-out after successful heartbeat message #795

Closed
iavinash opened this issue Apr 17, 2024 · 0 comments
Closed

FIX connection timed-out after successful heartbeat message #795

iavinash opened this issue Apr 17, 2024 · 0 comments
Labels

Comments

@iavinash
Copy link

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 the quickfix_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

@iavinash iavinash added the bug label Apr 17, 2024
@quickfix-j quickfix-j locked and limited conversation to collaborators Apr 17, 2024
@chrjohn chrjohn converted this issue into discussion #796 Apr 17, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests

1 participant