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.

Sign up for GitHub

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

Jump to bottom

[FIXED] natsConnection_RequestMsg() incorrectly returns NATS_NO_SERVER_SUPPORT #645

Merged
merged 3 commits into from
Mar 9, 2023
Merged

[FIXED] natsConnection_RequestMsg() incorrectly returns NATS_NO_SERVER_SUPPORT #645

merged 3 commits into from
Mar 9, 2023
+23 −1

Commits on Mar 9, 2023

  1. [FIXED] natsConnection_RequestMsg() incorrectly returns NATS_NO_SERVE… 

    …R_SUPPORT

When using `natsOptions_SetRetryOnFailedConnect` option to connect
and the library is not yet connected, calling `natsConnection_RequestMsg`
with a message with headers would incorrectly return `NATS_NO_SERVER_SUPPORT`
instead of `NATS_TIMEOUT`.

Resolves #644

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
    @kozlovic
    kozlovic committed Mar 9, 2023
    Configuration menu
    Copy the full SHA
    3c64f4a View commit details
    Browse the repository at this point in the history

  2. Added a comment 

    Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
    @kozlovic
    kozlovic committed Mar 9, 2023
    Configuration menu
    Copy the full SHA
    0fc7710 View commit details
    Browse the repository at this point in the history

  3. Fix other possible STAN flappers 

    Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
    @kozlovic
    kozlovic committed Mar 9, 2023
    Configuration menu
    Copy the full SHA
    5111033 View commit details
    Browse the repository at this point in the history