Problem with ODP.NET on Windows 2000

[tal.brown]

Hi,

I wrote a simple application that opens and closes connections to an
Oracle DB using the standard ODP.NET API. The ODP version is
2.102.2.20 and the DB version is 9.2.0.7

This application works fine on Windows XP, but when running on Windows
2000 (SP4) it takes about and hour and finally the application hangs
on 100% CPU.
I monitored the application using perfmon, specifically the CLR
Exceptions statistic. It appears that each time I open a connection
(this happens with and without connection pooling) a CLR Exception
occurs and is caught internally, so I can't analyze it.

Has anyone seen this issue before or heard of specific Win 2000
problems with ODP.NET ?

Thanks...

 

[Frans Bouma [C# MVP]]

Hi,

I wrote a simple application that opens and closes connections to an
Oracle DB using the standard ODP.NET API. The ODP version is
2.102.2.20 and the DB version is 9.2.0.7

This application works fine on Windows XP, but when running on
Windows 2000 (SP4) it takes about and hour and finally the
application hangs on 100% CPU.
I monitored the application using perfmon, specifically the CLR
Exceptions statistic. It appears that each time I open a connection
(this happens with and without connection pooling) a CLR Exception
occurs and is caught internally, so I can't analyze it.

Has anyone seen this issue before or heard of specific Win 2000
problems with ODP.NET ?

Do you start a lightweight transaction which can be distributed?
(system.transactions support) or an enterprise services transaction?

ALso, as you're using 9i, it could be wise to use the 9.2.0.7 ODP.NET
for that db.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------