SingalR Resource started replying with 500

Georgios Arslanoglou 1 Reputation point
2020-09-10T12:03:10+00:00

SingalR Resource started replying with 500.

Without any actions from my side, the SignalR resource of my AppService started responding with 500.
After 2 restarts of the resource, it started responding with this:
Service returned handshake error: Maximum message count limit reached: 20000. Id: 9f1802e1-65cd-47fd-b7d2-a90ad17cb0e6

The high number of messages are due to the automatic reconnects that the appservice tried to do. It's an extremely low traffic app service, with 100 messages max per day.

The same error continues even after I switched off the Azure Signal R resource and tried to serve the SignalR requests from the AppService itself.

Subscription ID: 89ef4cc1-31c7-4009-aa26-cc3bd5c1086a

Signalr resource: SignalRSimpleChatservice
AppService: SignalRSimpleChat20200822030641

Azure SignalR Service
Azure SignalR Service
An Azure service that is used for adding real-time communications to web applications.
131 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Georgios Arslanoglou 1 Reputation point
    2020-09-10T12:20:15.207+00:00

    Actually after I deleted all the Configuration properties regarding Azure SignalR and removing completely the relevant entry from the appSettings.json, now SignalR requests are served from the AppService and everything works.

    I guess the Azure.SignalR resource in France Central experienced some infrastructure issues, so you should definitely check it out anyway.

    0 comments
  2. SnehaAgrawal-MSFT 19,921 Reputation points
    2020-09-11T05:48:42.477+00:00

    Thanks for asking question! The SignalR resource is a free tier instance which has a message limit of 20000 per day. According to our backend metrics there are many messages being sent, may be different than what expected (for example large message may be split into smaller ones and counted as multiple messages), which has caused connections get throttled.

    Please refer to below doc about how messages are counted in SignalR service:

    https://video2.skills-academy.com/en-us/azure/azure-signalr/signalr-concept-messages-and-connections

    To add to this if the message count is expected then the only solution is to scale the instance to Standard tier which doesn’t have a hard message count limit.

  3. Georgios Arslanoglou 1 Reputation point
    2020-09-16T19:55:39.567+00:00

    The thing is, that before the peak of messages, the SignalR resource stopped responding.
    Anyway, a lot of days have passed, so I guess it's impossible to track down what happened then.

    I'll keep in mind that the free tier comes with those limits.

    Thanks for your answer.

    0 comments