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

Client fails to reconnect after server downtime #87

Open
camille-bouvy-frequenz opened this issue Dec 23, 2024 · 2 comments
Open

Client fails to reconnect after server downtime #87

camille-bouvy-frequenz opened this issue Dec 23, 2024 · 2 comments
Assignees
Labels
part:tooling Affects the development tooling (CI, deployment, dependency management, etc.) priority:❓ We need to figure out how soon this should be addressed type:bug Something isn't working

Comments

@camille-bouvy-frequenz
Copy link
Collaborator

What happened?

When running tests with the trading app, we tried stopping and restarting the server in order to ensure that the trading app would be able to reconnect once it is back online. However, we observed that the Client was not able to reconnect to the service (even after >5min).

What did you expect instead?

We expected the API Client to connect back to the server once it is back online (most likely in 60secs since it is the keepalive default).

Affected version(s)

v0.3.1

Affected part(s)

Build script, CI, dependencies, etc. (part:tooling)

Extra information

It seemed to work in the past, we're unsure if this could be related to the latest update of the base client (since this is where keepalive is implemented).

@camille-bouvy-frequenz camille-bouvy-frequenz added priority:❓ We need to figure out how soon this should be addressed type:bug Something isn't working labels Dec 23, 2024
@keywordlabeler keywordlabeler bot added the part:tooling Affects the development tooling (CI, deployment, dependency management, etc.) label Dec 23, 2024
@camille-bouvy-frequenz
Copy link
Collaborator Author

FYI @llucax

@llucax
Copy link

llucax commented Jan 3, 2025

Mmm, interesting. If you can find a way to reproduce it consistently can you try with and without keepalive to see if it is related to that (my guess is keepalive should help to re-connect, not the other way around), you can enable and disable keepalive via the connect URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part:tooling Affects the development tooling (CI, deployment, dependency management, etc.) priority:❓ We need to figure out how soon this should be addressed type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants