My Oracle Support Banner

System.AccessViolationException when using CommandTimeout in ODP.NET (Doc ID 1377275.1)

Last updated on JULY 05, 2017

Applies to:

Oracle Data Provider for .NET - Version and later
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)

***Checked for relevance on 10-Oct-2016***


Using CommandTimeout with the Oracle Data Provider for .NET (ODP.NET) may result in a System.AccessViolationException and application crash in certain versions of ODP.NET when the operation times out.

A sample stack is as follows:

at Oracle.DataAccess.Client.OpsSql.Timeout(OpoSqlValTimeoutCtx& opoSqlValTimeoutCtx)
at Oracle.DataAccess.Client.OracleCommand.Timeout(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.