Memory Error with latest version

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Memory Error with latest version

Post by crazypit » Mon 25 Oct 2010 07:28

Hello,

I use the latest version of dotConnect for Oracle in a Windows Service application. Last night, the service went down due to an unhandled exception. The error propagated to the Event Viewer where the following information is logged:

Application: Exis.eXray.AppServerService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
at System.Runtime.InteropServices.GCHandle.get_Target()
at Devart.Data.Linq.c.j()
at Devart.Data.Linq.i.a(Int32)
at Devart.Data.Linq.g.a(a)
at Devart.Data.Linq.g+a.b()

The only thing i can provide as a help, is that i use the:





configuration for my service.

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Mon 25 Oct 2010 08:18

Error message is : Handle is not initialized.

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Tue 26 Oct 2010 08:11

Again last night, with the exact same stack trace...

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Tue 26 Oct 2010 08:43

The problem appears to be caused by the peculiarities of the Garbage Collector work. If this issue can be reproduced more or less reliably, please send us a test project so that we are able to investigate it in details.

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Tue 26 Oct 2010 08:58

This Windows Service is our Application Server for our CRM system. The solution has 23 different projects, 10 of which are console applications loaded in different application domains according to user preferences. Most of these console applications, host WCF services.

It is apparent that there is no way i can create a test project for this! For simple projects, everything works ok. The complexity is the problem.

I can give you more information about the way our application server is architectured if you like. I can provide you with our Team Licence information if you think that maybe i don't deserve better attention, i can switch to email and abandon the forum, but PLEASE, PLEASE, don't ask about a test project for a Garbage Collector related error!!!

bmarotta
Posts: 34
Joined: Wed 29 Sep 2010 11:27

Post by bmarotta » Tue 26 Oct 2010 10:28

I have this error also from time to time on our IIS server on version 5.60.124. This occurs in some background thread and completely crashes the server with no error message.

It looks like dotConnect for Oracle does not work quite well on heavy multithread load.

As you cannot reproduce it, why don't you just catch this error and handle it. Output something and on some log file and don't crash the application.

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Tue 26 Oct 2010 13:07

We are going to implement catching this exception in our code. We will inform you here when the corresponding build is available.

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Thu 04 Nov 2010 11:08

Service is crashed every 2-3 days. I switched to Workstation GC configuration and the problem persists.

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Fri 05 Nov 2010 15:32

Please try the latest 5.70.190 build of dotConnect for Oracle. It can be downloaded from
http://www.devart.com/dotconnect/oracle/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/

Please tell us if the problem can be reproduced with it.

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Wed 10 Nov 2010 08:54

Problem still persists using the latest dotConnect for Oracle with exactly the same stack trace. Service is crashed every 2-3 days. The versions used in my application are:

Devart.Data 5.0.143.0
Devart.Data.Linq 1.0.43.0
Devart.Data.Oracle 5.70.190.0
Devart.Data.Oracle.Linq 1.0.43.0

Please, i really need this fixed because it's getting really embarassing...

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Wed 10 Nov 2010 11:31

We've made some changes that should fix the issue. These changes will be available in the Beta build which we will release in several days. We will inform you when this build is published.

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Thu 11 Nov 2010 17:24

Please try the 6.0.46 Beta build of dotConnect for Oracle. It includes the changes that should fix the problem. The build can be downloaded from
http://www.devart.com/dotconnect/oracle/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/

For the detailed information about the fixes and improvements implemented in dotConnect for Oracle Beta 6.0.46, please refer to
http://www.devart.com/forums/viewtopic.php?t=19496

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Thu 18 Nov 2010 07:54

I tried the latest beta version but i hit the error described by me on an other message : http://www.devart.com/forums/viewtopic.php?p=63226. This prevents me from using the beta version in production environment, so i'm stuck with the problem. I hope that you will fix my issue as soon as possible in the next minor release of 5.XX line which i hope will be more stable than the new 6.XX line.

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Tue 23 Nov 2010 14:16

Problem now happens 2-3 times a day!It seems that the frequency is analogous to the load of my server. Please, i need a customized 5.70.190 version with the problem fixed ASAP!

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Tue 23 Nov 2010 14:44

We've answered you in this topic:
http://www.devart.com/forums/viewtopic.php?t=19524

Please tell us if the problem with the Beta 6.0.46 version persists.

Post Reply