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

reconnect_interval does not seem to have any affect #102

Open
wmmihaa opened this issue Mar 1, 2023 · 1 comment
Open

reconnect_interval does not seem to have any affect #102

wmmihaa opened this issue Mar 1, 2023 · 1 comment

Comments

@wmmihaa
Copy link

wmmihaa commented Mar 1, 2023

Describe the bug
I've set up my connection as following:

self.connection = HubConnectionBuilder()\
    .with_url(signalr_uri, options={"verify_ssl": False}) \
    .with_automatic_reconnect({
        "type": "raw",
        "enable_trace": False,
        "keep_alive_interval": 15,
        "reconnect_interval": 2000
    }).build()

When the client gets disconnected from the hub, it will continuously try to re-connect, but with no delay. I first tried using "interval" and set the interval to an array of integers [1,2,3,4,5], but the same thing happend although it stopped after five tries. I was not sure if the actual number was in seconds or milliseconds so I also tried with [1000,2000,3000...] but with the same result, no delay.

BTW... are all connection settings i seconds?

(but thanks for everything else ;) )

@SipanOhanyan
Copy link

It will be fixed after #114 pull request merge.

SipanOhanyan added a commit to lynxal/signalrcore that referenced this issue Nov 13, 2024
reconnect_interval does not seem to have any affect mandrewcito#102
Reconnect logic spamming logs and creating threads until resource exhaustion occurs mandrewcito#97
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

No branches or pull requests

2 participants