Skip to content
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.

Sign up for GitHub

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

Jump to bottom

SQL Server: Should retry on 203 #33260

Closed
AndriySvyryd opened this issue Mar 6, 2024 · 0 comments
Closed

SQL Server: Should retry on 203 #33260

AndriySvyryd opened this issue Mar 6, 2024 · 0 comments
Labels
area-aspire area-execution-strategies closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. customer-reported Servicing-approved type-bug
Milestone
8.0.4

Comments

@AndriySvyryd
Copy link
Member

On Mac (and potentially Linux) a transient error is thrown that isn't retried by the built-in retry strategy:

Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - 20) ---> System.ComponentModel.Win32Exception (203): Unknown error: 203 at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

See dotnet/aspire#1023
@AndriySvyryd AndriySvyryd mentioned this issue Mar 6, 2024
Closed
AndriySvyryd added a commit that referenced this issue Mar 7, 2024
@AndriySvyryd
Retry on 203
6432c78 
Fixes #33260
@AndriySvyryd AndriySvyryd mentioned this issue Mar 7, 2024
Merged
AndriySvyryd added a commit that referenced this issue Mar 7, 2024
@AndriySvyryd
Retry on 203
f309bb8 
Fixes #33260
@AndriySvyryd AndriySvyryd added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Mar 11, 2024
@AndriySvyryd AndriySvyryd added this to the 8.0.4 milestone Mar 11, 2024
@AndriySvyryd AndriySvyryd removed their assignment Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-aspire area-execution-strategies closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. customer-reported Servicing-approved type-bug
Projects
None yet
Milestone
8.0.4
Development

No branches or pull requests
2 participants
@ajcvickers @AndriySvyryd