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

Ugly delayed exceptions (error reading data from the connection) on certain driver versions in VS2013 / all versions in VS2015 [DNET655] #612

Closed
firebird-automations opened this issue Dec 8, 2015 · 6 comments

Comments

@firebird-automations
Copy link

Submitted by: Jimmy Gee (kraftmeister)

Attachments:
2015-10-19_01h01_07.jpg

I have isolated all my Firebird code into a single webservice module and are using very basic using() { } pattern to access the database.
The error happens sporadic after some time (if it happens) but is reproducable in the way that you can sort of guarantee that it will start happening after some hours max.
As soon as I use Visual Studio 2013 and driver version 4.5.1.0 or below it will NEVER happen (running for days and weeks)
As soon as I use Visual Studio 2013 and driver version 4.6.0.0 or above it WILL happen (after minutes or hours max.) It is very BAD as soon as it happens!!
As soon as I use Visual Studio 2015 (no matter which driver version) it WILL happen!!
.Net Framework version 4.5 4.51 4.52 4.6 does NOT matter!!

sample code:

using (var context = new VodmateEFCtx())
{
return context.DOWNLOADS.SingleOfDefault(x => x.dlcode = "xxxxxx");
}

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-automations
Copy link
Author

Commented by: @cincuranet

Can you share some code or at least stack trace?

@firebird-automations
Copy link
Author

Commented by: Jimmy Gee (kraftmeister)

This is a screenshot of a stack trace when the error hits...
I hope this helps!

@firebird-automations
Copy link
Author

Modified by: Jimmy Gee (kraftmeister)

Attachment: 2015-10-19_01h01_07.jpg [ 12852 ]

@firebird-automations
Copy link
Author

Commented by: @cincuranet

The exception originates from BeginRequest. It's your code executing and your connection is broken (somebody/something closed it). Nothing that happens out of the blue sky.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: In Progress [ 3 ] => Closed [ 6 ]

resolution: Won't Fix [ 2 ]

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