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

SignalR Connection continuous reconnect due to MessagePack (version 5.0.1) #28632

Closed
teliu-ez opened this issue Dec 14, 2020 · 7 comments
Closed
Labels
area-signalr Includes: SignalR clients and servers ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Status: Resolved

Comments

@teliu-ez
Copy link

teliu-ez commented Dec 14, 2020

Describe the bug

I got an issue that signal will continuous reconnect when I update MessagePack to latest version(5.0.1). I can fix this issue by degrade MessagePack to version 3.1.10. Could someone help to take a look at this?.net core: 3.1. SignalR: 1.6.1
image

Exceptions (if any)

No exception found

Further technical details

ASP.NET Core version: 3.1
SignalR version: 1.6.1
IDE: visual studio

@mkArtakMSFT mkArtakMSFT added the area-signalr Includes: SignalR clients and servers label Dec 14, 2020
@BrennanConroy
Copy link
Member

Can you share what your Hub and client are doing? Does the issue repro outside of Azure SignalR?

@BrennanConroy BrennanConroy added the Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. label Dec 14, 2020
@teliu-ez
Copy link
Author

teliu-ez commented Dec 16, 2020

Here is client side hub setting.
image

the front end and the back end just pass some messages to each other.
This issue is only related to SignalR. I fix this by degrade MessagePack to version 3.1.10.

@ghost ghost added Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. and removed Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. labels Dec 16, 2020
@BrennanConroy
Copy link
Member

Likely a dupe of #28354
Can you show your server logs? There is probably something like "Failed to load System.Text.Encodings.Web 5.0.0"

@BrennanConroy BrennanConroy added Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. and removed Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. labels Dec 16, 2020
@teliu-ez
Copy link
Author

Thanks very much @BrennanConroy .
Including a reference to System.Text.Encodings.Web 5.0.0
Or
Downgrading your SignalR.MessagePack reference to 3.1
can fix my issue.

@ghost ghost added Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. and removed Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. labels Dec 17, 2020
@teliu-ez
Copy link
Author

I have a question is if the MessagePack (version 5*) is designed for .netcore 5 and MessagePack (version 3*) is designed for .netcore 3? @BrennanConroy

@BrennanConroy
Copy link
Member

Kind of, but not really. You're just hitting a bug with the System.Text.Json package and .net core 3.1.

@BrennanConroy BrennanConroy added ✔️ Resolution: Duplicate Resolved as a duplicate of another issue and removed Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. labels Dec 17, 2020
@ghost ghost added the Status: Resolved label Dec 17, 2020
@teliu-ez
Copy link
Author

Thanks.

@ghost ghost locked as resolved and limited conversation to collaborators Jan 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-signalr Includes: SignalR clients and servers ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Status: Resolved
Projects
None yet
Development

No branches or pull requests

3 participants