AddAzureSignalR() seems to be causing all results to be null in the response frames
See original GitHub issueHi, I’m seeing a strange issue that wasn’t happening a couple days ago when I started using azure-signalr.
Whenever I append .AddAzureSignalR() to services.AddSignalR() in ConfigureServices, all the frames of the incoming messages have null in the result.
{“type”:3,“invocationId”:“0”,“result”:null} {“type”:3,“invocationId”:“1”,“result”:null} {“type”:3,“invocationId”:“2”,“result”:null} …
The other day this was working, and I could see responses from both hubs (even posted screen shots on ticket 124). Currently though, neither hub works if UseAzureSignalR() is added. Even if UseAzureSignalR is removed, the normal hub still gets null results. If I remove AddAzureSignalR() from ConfigureServices, then the results all go start working as expected.
app.UseSignalR(routes =>
{
routes.MapHub<SignalRHub>("/signalr/hub");
});
// even if i remove this the normal hub doesn't work either
app.UseAzureSignalR(routes =>
{
routes.MapHub<SignalRHub>("/signalr/azurehub");
});
client-lib: aspnet/signalr: 1.0.0, server-libs: Microsoft.AspNetCore.SignalR: 1.0.1, Microsoft.Azure.SignalR: 1.0.0-preview1-10012 (also tried 10011 which is was i was using the other day, but it didn’t work either.)
client-logs.txt server-logs.txt
Thanks for any insights you can provide
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (8 by maintainers)
Top GitHub Comments
@stephenweaver we have decided to remove the size limit for sending from server to client. But you should expect poorer performance and longer latency when the message size goes bigger. This change is going to be rolled out later next week. I know you’re in a very tight schedule, so please let me know whether this time works for you.
Yeah, it gets tricky when using Azure SignalR Service.
In ASP.NET Core SignalR, you can observe the limitation from client. It means you can’t send a message larger than 32KB from client to server. But you can send message larger than 32KB from server to client. The reason is server has a pre-defined buffer size (default value is 32KB) to receive message. When message from client exceeds the buffer size, an exception will be thrown.
Then in Azure SignalR Service, your app server is essentially a client to service. Then the 32KB limitation kicks in when you want to send a message from server to client.