Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Disconnect event takes 10 minutes to trigger #39666
Comments
|
What version of the SignalR client are you using? Are you running the server under a debugger? |
|
Hi @bencz. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Describe the bug
I'm developing an ASP.Net core service that uses Signalr, an android app connects to the signalr HUB.
When performing the test of disconnecting the cell phone from the internet network, while it is connected to the HUB, there is a delay of 10 minutes to trigger the disconnect event on the server.
I'm currently using SignalR's default timeout settings.
The bug/feature is, the time that the SignalR uses to trigger the disconnect event.
According to the documentation this time should be just a few seconds.
Expected Behavior
The quick disconnect trigger.
Steps To Reproduce
Create some Hub with ASP.Net core and SignalR
Create some VM or Android APP that connect to the SignalR hub
Connect the app to the hub
Disconnect the VM or app machine from network
Exceptions (if any)
No response
.NET Version
6.0.101
Anything else?
No response
The text was updated successfully, but these errors were encountered: