You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Azure SignalR SDK within orchard module I'm not getting response for keep-alive request {"type":6}.
Everything works fine when switching to local SignalR.
Edit Startup.cs in Repro.TestModule and in SimpleMvc.Web by providing connection string to your AzureSignalR instance, .AddAzureSignalR("Endpoint=https://your-endpoint.signalr.net;AccessKey={your-access-key};Version=1.0;");
or comment out this line to run project without Azure SignalR Service,
Run Repro.Web project and check Network tab in your browser.
Exceptions (if any)
No exceptions just no response for ping request.
Further technical details
Azure SignalR SDK version 1.7.0
Server ASPNETCORE version 3.1.0
Your SignalR Client SDK version 5.0.2
Orchard Core version 1.0.0-rc2-15791
Connected Issue
I've also created bug in Orchard Core issue tracker, where you can find more (maybe usuful) details: OrchardCMS/OrchardCore#8409
The text was updated successfully, but these errors were encountered:
lampersky
changed the title
Azure SignalR Service SDK is not working within Orchard Core Module
Azure SignalR SDK is not working within Orchard Core Module
Jan 25, 2021
Orchard core doesn't support IHostedService, that's why HeartBeat service is registered but not started, and this is why we can observe missing keep alive message.
Describe the bug
When using Azure SignalR SDK within orchard module I'm not getting response for keep-alive request
{"type":6}
.Everything works fine when switching to local SignalR.
To Reproduce
(Repro project is made using dotnet cli, ocmvc + ocmodulemvc),
.AddAzureSignalR("Endpoint=https://your-endpoint.signalr.net;AccessKey={your-access-key};Version=1.0;");
or comment out this line to run project without Azure SignalR Service,
Exceptions (if any)
No exceptions just no response for ping request.
Further technical details
Connected Issue
I've also created bug in Orchard Core issue tracker, where you can find more (maybe usuful) details:
OrchardCMS/OrchardCore#8409
The text was updated successfully, but these errors were encountered: