Background Thread Unhandled InvalidOperationException again

Background Thread Unhandled InvalidOperationException again

Postby crazypit » Mon 16 May 2011 07:21

Hello,

Using the latest LinqConnect build 2.20.21, i still get the first unhandled exception as described in http://www.devart.com/forums/viewtopic.php?t=20504.

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 Devart.Common.DbConnectionInternal.d(System.Object)
at Devart.Common.DbConnectionPoolGroup.a(Devart.Common.DbConnectionPool)
at Devart.Common.DbConnectionPoolGroup.a(System.Object)
at System.Threading.ExecutionContext.runTryCode(System.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading._TimerCallback.PerformTimerCallback(System.Object)


System is an Oracle 11.2.0.1. We do not use Direct mode. We use the default Devart pooling with min 10 max 100 connections for each of a number of 5-6 application domains loaded in a Windows Service process. Oracle client used, is an Oracle Instant Client version 11.2.0.1. Database and application server are 2 different Windows Server 2008 R2 64-bit machines.
crazypit
 
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Postby StanislavK » Thu 19 May 2011 12:54

Sorry for the delay. We will investigate this situation and inform you about the results as soon as possible.
StanislavK
Devart Team
 
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Postby StanislavK » Thu 29 Sep 2011 16:25

Could you please specify if you are still encountering this error? Though we couldn't reproduce it, we can send you a test build with logging enabled to localize the error's cause.
StanislavK
Devart Team
 
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Postby crazypit » Wed 12 Oct 2011 12:42

Hello,

For the time being, we do not still encounter this error. We had some changes in our RAC configuration and setup and it seems that the problem went away.
crazypit
 
Posts: 163
Joined: Wed 15 Apr 2009 08:43


Return to LinqConnect (LINQ to SQL support)