I have the next setup in azure :
- One application gateway balancer
- Two virtual machines in the backend pool of the gateway .
- On the vms there is a signalr app deployed.
Problem :
When a client (browser) will invoke a method on a signalr hub server and the message size is aprox equal or grater then 70kb I receive (enabling logging on signalr client side) :
SignalR: Unclean disconnect from websocket: [no reason given]. SignalR: Closing the Websocket.
SignalR: Clearing hub invocation callbacks with error: Connection started reconnecting before invocation result was received.
SignalR: [server method] failed to execute. Error: Connection started reconnecting before invocation result was received.
Client is disconnected , after it tries to reconnect and send the message again. On reconnect I get a 101 HTTP response status from the server. Here are the logs:
SignalR: webSockets reconnecting.
SignalR: Connecting to websocket endpoint
SignalR: Closing the Websocket.
SignalR: Clearing hub invocation callbacks with error: Connection started reconnecting before invocation result was received.
SignalR: [server method] failed to execute. Error: Connection started reconnecting before invocation result was received. SignalR: webSockets reconnecting.
SignalR: Websocket opened.
Question : Does Azure Application Gateway has some limitations for the websockets message size ?
I tried this on a vm in Azure , by directly accessing IIS and I don't get the same error for the same message when I try to send it from the client to signalr hub .
I couldn't find any reference in azure application gateway documentation about max size for websockets messages.
Any help is appreciated.