Open
Description
When connection is closed from server-side (connection shutdown response, from i.e. DELETE FROM MON$ATTACHMENTS WHERE MON$ATTACHMENT_ID<>CURRENT_CONNECTION), the socket is no longer usable, yet the code puts the connection back to the pool (no IO problem happened yet). This means the connection will get back to application and application will for sure have to use retry logic to get new connection and continue doing what it was doing. Not a deal-breaker as retry logic should be there anyway, but it should be handled more pro-actively.
Taken from #1095.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
cincuranet commentedon Mar 3, 2023
cc @luronumen
[-]Cconnection shutdown connection should not go back to pool[/-][+]Connection shutdown connection should not go back to pool[/+]mrjohnr commentedon Jun 25, 2023
hi, any news about this issue? thanks
cincuranet commentedon Jun 25, 2023
Nope.
mrjohnr commentedon Jun 27, 2023
is that project abandoned ?no bugs fixed for a while, no Net 7 version, in about four moths Net 8 will be released and I'm still on Net 3.1(reached end of life/no longer supported) :(
cincuranet commentedon Jun 27, 2023
You're more than welcome to select a bug and fix it.
What from .NET 7 you need in provider (maybe better to continue in mailing list, instead of polluting this issue)? BTW EF7 is happening here, depending on my free time.