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
Error reading from connection : FirebirdSQL Connection Pooling (ADO.NET) is not Working [DNET667] #621
Comments
Commented by: alexedu (alexedu_2) This piece of code will allow you to see that connection pool doesn't work correctly after for example server instance rebooting / dropping connection from outside or etc using FirebirdSql.Data.FirebirdClient; namespace ConsoleClient
} |
Modified by: alexedu (alexedu_2)Version: 4.10.0.0 [ 10742 ] Attachment: FirebirdConsoleClient.zip [ 12893 ] description: Actual result: Expected Result: Steps to reproduce the issue: Additional Information: => The Connection Pooling should NOT USE broken connection This issue did not happen when using the previous http://ADO.NET Provider v.4.5.2.0. I attached small console app where you will be able to reproduce issue. environment: Firebird 2.5.3.26780 (x64); => Firebird 2.5.x Version: 4.6.0.0 [ 10640 ] => |
Commented by: alexedu (alexedu_2) I also will take a look to the FbConnectionPoolManager. |
Commented by: alexedu (alexedu_2) Information about SQL Server connecting pooling If SQL Server stops all connections currently in pool will be broken. Connection pool doesn't validate the state of the connection. You will most probably get exception for each broken connection but next calls will create new connection and CRUD operations will work again. As you can see SQL Server will create new connection and CRUD operations will work again. |
Modified by: @cincuranet |
Submitted by: alexedu (alexedu_2)
Duplicates DNET585
Attachments:
FirebirdConsoleClient.zip
The Connection Pooling should NOT USE broken connection
This issue did not happen when using the previous http://ADO.NET Provider v.4.5.2.0.
I attached small console app where you will be able to reproduce issue.
The text was updated successfully, but these errors were encountered: