Error server timeout elapsed without receiving a message from the server

Hi

Dedicated Signal R — yes as you saw.

«Also, are you deploying to a single region within Azure and accessing from different continents?:»
Yes 1 single region only — North Central US — that was working ok until about 2 to 3months ago in Asia — customer reports — Australia is unusable but was ok prior. Singapore not bad on and off a few an hour or more. Thailand is very sketchy — maybe a submarine cable was damaged or something regional changed with networks.

Client to Server ping times are 15ms to 30ms average — but line quality im not sure- jittering and so on.

Side by side tests
I have run other blazor websites alongside it hosted in the USA — such as https://blazorhelpwebsite.com/ and blazotrain.com but no errors on those — even on pages with no dynamic elements.

Ok Noted: So we could use geo region web servers with Azure

«Another thing to check is if there is a way to increment the timeout settings on the client, since I believe what is failing is the ping mechanism. @BrennanConroy is this possible?»
This sounds like a good idea will wait for the answer on that one. — i have provided the program.cs.txt with some settings in it etc.

builder.Services.AddSignalR().AddAzureSignalR(options =>
{
options.ServerStickyMode = Microsoft.Azure.SignalR.ServerStickyMode.Required;
options.MaxPollIntervalInSeconds = 10;
});
is this related?

«Does the connection recover or do you need to refresh the page to make it go away? Does the problem persist after refreshing the page?»

the system always manages to reconnect 99% of the time.
After a refresh the problem comes back
After a service restart the problem also persists.
The problem is the same on any page with static or dynamic content.

some settings here:
Program.cs.txt.txt

Browser Network:

Further tests this end:

1. Remove server signal R and make a local debug version run test to prove its not a code based issue or Signal R Server issue
   2)Create a blank website first and see what the out of the box blazor does alongside from the same app server alongside the problematic — to verify its not a rogue webiste code base etc.
   3)Geo located server test
   4)remove google analytics etc

Timeout expired messages when connecting to SQL Server

Applies to: В SQL Server

Before you start troubleshooting, check the prerequisites and go through the checklist.

A timeout error means that a certain operation takes longer than needed. The client application stops the operation (instead of waiting indefinitely), which may block other operations and suspend an application. This article provides resolutions for «command-timeout» and «connection-timeout» errors you receive when you connect to SQL Server.

Verify timeout expired errors

When you encounter «timeout expired» issues, you receive one or more of the following error messages:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgment. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was [Pre-Login] initialization=23; handshake=14979;
System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out.

System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out.

Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgment. This could be because the pre-login handshake failed or the server was unable to respond back in time.
The duration spent while attempting to connect to this server was [Pre-Login] initialization=21036; handshake=0; (Microsoft SQL Server, Error: -2).

System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool.

If connections aren’t closed correctly, errors may occur. These errors occur because all pooled connections are in use, and max pool size is reached. You can avoid these errors if you follow the steps described in the exhausted the connection pool article.

The second and the third error occur when .NET Framework 4.5 or a later version is installed.

Determine the type of timeout expired errors

From a connectivity perspective, you encounter the following timeout issues:

• Connection timeout (15 seconds by default)
• Query or command timeout (30 seconds by default)

The default values can be set through code, connecting string, or other methods.

Before troubleshooting, view the complete call stack of the error messages to determine the error type.

See the following example of a call stack of a connection timeout:

SqlConnection.Open indicates that the client is trying to open a connection and therefore isn’t related to a query.

See the following example of a call stack of a query or command timeout:

The SqlCommand class is used to work with a query, not a connection. The ExecuteScalar method is used to run a query. You can also see other items, such as an ExecuteReader or ExecuteNonQuery .

Troubleshoot timeout expired errors

If you encounter a query or command-timeout error, see Troubleshoot query time-out errors.

If you encounter a connection-timeout error, follow the steps:

Increase the connection-timeout parameter.

If you use an application to connect to SQL Server, increase the relevant connection-timeout parameter values and check whether the connection eventually succeeds. For example, if you use System.Data.Sqlcient , set the SqlConnection.ConnectionTimeout property to 30 or a higher value.

If you use SQL Server Management Studio (SSMS), select the Connection Properties tab in the Connect to Server dialog box, and set Connection time-out setting to a higher value.

If the connection eventually succeeds, it’s a network issue. You need to work with your network administrator to resolve the issue. After it’s resolved, you can revert to default settings in your application.

Increasing the connection timeout in the application is a possible method, but it isn’t a long-term resolution. This is because the connection occurs quickly (usually within a few milliseconds) when you try to connect to a data source.

Typical causes and resolutions for the error

The following table lists typical causes and resolutions for timeout expired errors. For more tips and suggestions, see Troubleshooting: Timeout Expired.

Источник

Connection disconnected with error ‘Error: Server timeout elapsed without receiving a message from the server.’. #42778

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Client Disconnect reconnect message on browser multiple times per minute in some cases

Very frequent disconnect reconnect issues that make the system unusable — unless very close proximity in the USA.
reports in other country’s unusable — in Asia
Asia regions were stable prior .e.g. it could go all night no disconnect on soak tests.
but for the last 2 to 3months this is very bad. i have attempted to add code server side config forced sticky sessions and so on and on the app config side

This occurs within local debugging Dev, Stage and Production so im assuming its related to signalr connection.

i tried pretty much all of the info on the web i could find over many weeks, before submitting this issue- but to no avail as yet.
So i thought i would drop you a line thank you in advance

have gone all in on Azure + Blazor so this is mission critical for us 🙂

Expected Behavior

very few disconnects if at all.

Steps To Reproduce

Navigate to from an Geo Asia location:
https://alphawebtrader.azurewebsites.net/
open a web console and view the output
wait for disconnect reconnect

Exceptions (if any)

Error: Connection disconnected with error ‘Error: Server timeout elapsed without receiving a message from the server.’.

.NET Version

Anything else?

Visual Studio 2020

The text was updated successfully, but these errors were encountered:

@MicroTrendsTom thanks for contacting us.

Are you using Azure SignalR service to scale-out the connections?

Nevermind, I saw it on your settings.

Also, are you deploying to a single region within Azure and accessing from different continents?

The first thing we would recommend would be to try to put servers closer to where your users are. Given that Blazor is a real-time framework, traffic across continents can make the experience suffer, since at such distances, even at the speed of light you have limitations, so each server roundtrip can result in a few hundred milliseconds of latency.

Another thing to check is if there is a way to increment the timeout settings on the client, since I believe what is failing is the ping mechanism. @BrennanConroy is this possible?

It might also help to capture the network traffic to try and detect if something is going on at the server when these things happen. (Is the app restarting/the server rebooting? Which will cause the existing circuits to get destroyed)

Does the connection recover or do you need to refresh the page to make it go away? Does the problem persist after refreshing the page?

Hi @MicroTrendsTom. We have added the «Needs: Author Feedback» label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then — please feel free to re-open it if you come back to this issue after that time.

Dedicated Signal R — yes as you saw.

«Also, are you deploying to a single region within Azure and accessing from different continents?:»
Yes 1 single region only — North Central US — that was working ok until about 2 to 3months ago in Asia — customer reports — Australia is unusable but was ok prior. Singapore not bad on and off a few an hour or more. Thailand is very sketchy — maybe a submarine cable was damaged or something regional changed with networks.

Client to Server ping times are 15ms to 30ms average — but line quality im not sure- jittering and so on.

Side by side tests
I have run other blazor websites alongside it hosted in the USA — such as https://blazorhelpwebsite.com/ and blazotrain.com but no errors on those — even on pages with no dynamic elements.

Ok Noted: So we could use geo region web servers with Azure

«Another thing to check is if there is a way to increment the timeout settings on the client, since I believe what is failing is the ping mechanism. @BrennanConroy is this possible?»
This sounds like a good idea will wait for the answer on that one. — i have provided the program.cs.txt with some settings in it etc.

builder.Services.AddSignalR().AddAzureSignalR(options =>
<
options.ServerStickyMode = Microsoft.Azure.SignalR.ServerStickyMode.Required;
options.MaxPollIntervalInSeconds = 10;
>);
is this related?

«Does the connection recover or do you need to refresh the page to make it go away? Does the problem persist after refreshing the page?»

the system always manages to reconnect 99% of the time.
After a refresh the problem comes back
After a service restart the problem also persists.
The problem is the same on any page with static or dynamic content.

Browser Network:

Источник

Error «Server timeout elapsed without receiving a message» while calling the invoke method of signalr hubconnection #39811

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

If I open the devtools of browser, the invoke method of signalr connection will always throw the timeout error.
If I don’t open the devtools, the invoke method can receive response message.
C# code about hub:

Expected Behavior

The invoke method can get response message.

Steps To Reproduce

• Run client with browser, and open devtools of browser
• Run signarl server
• Refresh the browser to build hubconnection

Exceptions (if any)

[2022-01-27T08:51:13.283Z] Error: Connection disconnected with error ‘Error: Server timeout elapsed without receiving a message from the server.’.

.NET Version

Anything else?

The text was updated successfully, but these errors were encountered:

Use chrome, it is ok
The bug occurred when using microsoft.edge

Does this happen all the time?
Are you running the server under a debugger?
Can you share Trace level server logs that show the SignalR connection? https://docs.microsoft.com/aspnet/core/signalr/diagnostics?view=aspnetcore-6.0#server-side-logging

Hi @ZhibingGe. We have added the «Needs: Author Feedback» label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then — please feel free to re-open it if you come back to this issue after that time.

Can you check if maybe you have set network throttling and that’s why it doesn’t work when you open dev tools? I have the same issue with throttled connections. Related: #39885

I have same issues, server seems work correctly:

and here are logs from js client:

SSE often has issues when you host your app behind a proxy that buffers responses. You should check your proxies config to see if it’s doing that.

Skipping transport ‘WebSockets’ because it was disabled by the client.

It also looks like you’re explicitly not using WebSockets which is a bit odd, you should try using WebSockets or LongPolling and see if those work for you.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

Does this happen all the time? Are you running the server under a debugger? Can you share Trace level server logs that show the SignalR connection? https://docs.microsoft.com/aspnet/core/signalr/diagnostics?view=aspnetcore-6.0#server-side-logging

When using Microsoft Edge browser, it happens all the time. And the log from server side seems ok, In debug mode, the server has executed invoked method and return related info. The trace please see @nrmtmt comments.

Provide a minimal app as a GitHub repo that reproduces the issue and share the version of Edge you see the problem in.

Hi @ZhibingGe. We have added the «Needs: Author Feedback» label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then — please feel free to re-open it if you come back to this issue after that time.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

Works on the latest MicrosoftEdge version(V98.0.1108.50)

Hi all.
We have a similar issue with «@microsoft/signalr» version 6.0.2.

With Firefox everything is working fine.

The client connection to the server hub is pending and does not complete using Chrome/Edge. The onConnectedAsync() hub side method is never called with Chrome/Edge.

After several seconds with Chrome/Edge we have these errors:

Any ideas?
Thanks for your support

I can confirm this behaviour impact also Chrome, in applications compiled for NET 5.0, running on a machine having both NET 5.0 and NET 6.0 installed.

These are the versions of SignalR JS client where we are experiencing the problem:

There are the installed frameworks

Our application is using these NuGet packages (i took out from the list the non-relevant ones):

Источник

Problem

After connecting Jira to Microsoft Teams, the following symptoms may be displayed:

• The app shows disconnected either immediately or a short time later.  The longest reported connection was less than 24 hours. 

• You may see in incrementing number of open files for Jira.  

• You may see an incrementing number of open threads in Jira.  

One of the following appears in the atlassian-jira.log:

ERROR ServiceRunner [c.microsoft.signalr.HubConnection] HubConnection disconnected with an error: Server timeout elapsed without receiving a message from the server.. 
ERROR [c.microsoft.signalr.HubConnection] HubConnection disconnected with an error: Server timeout elapsed without receiving a message from the server..

ERROR ServiceRunner [c.m.teams.service.SignalRService] startConnectionIfDisconnected() error (java.lang.RuntimeException): Unexpected status code returned from negotiate: 503 Service Unavailable. 

This may appear as thousands of threads in a thread dump or in the catalina.out log:

Ok Http WebSocket https://msteams-jira-server.service.signalr.net/... priority:5 - 
threadId:0x0000000000001784 - nativeId:0 - nativeId (decimal):0 - state:WAITING 
stackTrace: java.lang.Thread.State: WAITING (parking) 
at java.base@11.0.6/jdk.internal.misc.Unsafe.park(Native Method)

Diagnosis

Environment

• Jira Server deployment

• Connected to Teams via the MS Teams app and/or a Teams webhook

Diagnostic Steps

• Install the MS Teams app. 

• Configure the connection.
• When the app disconnects, you may see: 
  • the stacktraces above. 
  • an Out Of Memory exception even though there is enough heap space for Jira. 
  • a «too many open files» exception if Jira hits the ulimit for open files.

Cause

The Teams app appears to open connections without releasing or closing them.  It will then attempt to open another new connection without closing the first. 

Workaround

Completely uninstall the Teams app and Jira integration from both sides.  Simply disabling the app has been shown to not stop threads from incrementing.  

Resolution

There is no resolution at this time.

Note

Please watch the bug report below for updates

• JRASERVER-71373 — Using MS Teams in Jira spawns incremental unclosed threads