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.

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

Connection resiliency [DNET668] #622

Closed
firebird-issue-importer opened this issue Feb 2, 2016 · 14 comments
Closed

Connection resiliency [DNET668] #622

firebird-issue-importer opened this issue Feb 2, 2016 · 14 comments

Comments

@firebird-issue-importer
Copy link

firebird-issue-importer commented Feb 2, 2016

Submitted by: @cincuranet

Relate to DNET585
Relate to DNET678
Relate to DNET591
Is related to DNET807
Is replaced by DNET818

Votes: 3

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 2, 2016

Modified by: @cincuranet

Link: This issue relate to DNET585 [ DNET585 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 27, 2016

Commented by: @luronumen

This issue is still reproducible on http://ADO.NET Provider v.5.0.5.0!
Please increase this bug priority once that since the version 4.6.0.0 in 11/Jan/15 Connection Pooling is not working (See: DNET585)

Best Regards,
Luciano

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 29, 2016

Commented by: @cincuranet

Propose some implementation in list and let's start the discussion.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 29, 2016

Commented by: @luronumen

Hi Jiri,

I think that we already have the solution once that this issue was introduced on v4.6.0.0 and this issue was not reproducible on http://ADO.NET Provider v.4.5.2.0.
Do you still have the source code of that version?

Best Regards,
Luciano

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 29, 2016

Commented by: @cincuranet

That implementation had nothing to do with connection resiliency.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 29, 2016

Commented by: @luronumen

Well, I was talking about the related issue DNET585 of this "New feature" issue.
Since there, no one is getting use Connection Pooling and I have disabled Connection Pooling in all of my .NET applications. :(

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Aug 21, 2016

Modified by: @cincuranet

Link: This issue relate to DNET678 [ DNET678 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 10, 2017

Modified by: @cincuranet

Link: This issue relate to DNET591 [ DNET591 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 12, 2018

Modified by: @cincuranet

Link: This issue is related to DNET807 [ DNET807 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 14, 2018

Modified by: @cincuranet

Link: This issue is replaced by DNET818 [ DNET818 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 14, 2018

Modified by: @cincuranet

status: Open [ 1 ] => Closed [ 6 ]

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 14, 2018

Commented by: @cincuranet

Replaced by DNET818. *Generic* connection resiliency is not possible on the library level.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 14, 2018

Modified by: @cincuranet

status: Closed [ 6 ] => Reopened [ 4 ]

resolution: Fixed [ 1 ] =>

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 14, 2018

Modified by: @cincuranet

status: Reopened [ 4 ] => Closed [ 6 ]

resolution: Fixed [ 1 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants