Skip to content
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

Bug: For Logon/Logout/Resend/SequenceReset messages we should wait until sent #628

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

AlexandrosKyriakakis
Copy link
Contributor

Issue

When log on request was queued because cannot be send due to connection not ready,
Then it goes through the main session
loop
which leads to
SendAppMessages

But, since session is not logged on yet because the message queued is the log on message, we drop the toSend queued messages so we lose the log on message itself.

Proposed solution

For important messages like Logon/Logout/Resend/SequenceReset we block until sent.

…til sent (#21)

## Issue 
When log on request was queued because cannot be send due to connection
not ready,
Then it goes through the [main session
loop](https://github.com/alpacahq/quickfix/blob/5dcde41f3e6e68e93e1fd381761cd9c7843aec43/session.go#L821-L841)
which leads to
[SendAppMessages](https://github.com/alpacahq/quickfix/blob/5dcde41f3e6e68e93e1fd381761cd9c7843aec43/session_state.go#L107-L111)

But, since session is not logged on yet because the message queued is
the log on message, we drop the `toSend` queued messages so we lose the
log on message itself.


## Proposed solution
For important messages like Logon/Logout/Resend/SequenceReset we block
until sent.
@ackleymi ackleymi merged commit 21eab6b into quickfixgo:main Apr 23, 2024
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants