-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hung at connection.open #165
Comments
@omhappy, what version of .NET are you using? I do see code you're referring to like: |
It's in the latest System version so it's likely to be the same in the Microsoft version. It should probably check for 0 on the read and then bail out for the caller to handle the incomplete packet. |
I use .Net Core 2.1 the code is |
Closed in error. |
This issue occurred frequently in one of our customer environment. when the issue occurs, we could see the high CPU utilization of the thread which call stack is like the below: (lldb) clrstack (lldb) dumpobj 00007f91f29ebee8 we could see for the SslOverTdsStream instance which _encapsulate is 1, so it is very obvious thread went into endless loop as the below code when readBytes always returns zero ( the customer said it will return zero always when connection disconnected)
... Could fix it by breaking the loop when the readbytes returns zero? It has been opened for a long time and when the issue can get fixed? Any ETA? |
Fixed with #577 - closing. |
I have an app in Azure AKS container. When the app call connection.open to connect to Azure Sql, it hung at ReadInternal method of class SslOverTdsStream occasionally.
We create a dump and find that the ReadInternal method doesn't check the return value of _stream.Read.
if the socket is closed, the return value is 0, then the method will be an infinite loop.
The text was updated successfully, but these errors were encountered: