Dataadapter.fill hangs in the debugger

Question

Hello all,

I have a .NET website that I am developing using Visual Web Developer 2008. This application  has a SQL select query which gets about 20,000 records from the database. When I try to use the debugger in Visual Web Developer Express edition 2008, the code hangs forever at the dataadapter.fill method. I tried to put some filters in the SQL query to get fewer records and it works fine for 200 records. My machine configuration is below. But when I try to run the same code in the development server, then it finishes fine with 20,000 records and gets the desired results.

The wierd part is that this program used to load the data perfectly fine in debugger until last week when my laptop crashed. So I had to reimage my hard disk and reinstall all software programs. After that, I have tried a number of different alternatives but none of them are making the debugger to work. If any one has faced similar problems, please let me know and it would be of tremendous help.

Thanks a ton.

Tech details:

.NET Framework: 3.5 SP1
Visual Web Developer edition: 2008
Start Options (Website-->Start Options in VWD): .NET 3.5 (tried with .NET 2.0 also)

Laptop Configuration:

RAM : 1 GB
Processor: AMD Turion (795 MHz)

Code (that hangs in debugger):

            string strSql = @"SELECT * FROM BIG_TABLE";
            OracleConnection con = new OracleConnection();
            DBConnector.AutoConnectStatic(con);  ----> User defined method that gets a connection object from the pool. This line works fine
            OracleDataAdapter da;
            DataSet ds;
            DataTable dt=new DataTable();

            da = new OracleDataAdapter(strSql, con);
            ds = new DataSet();
            da.Fill(ds); --------------> Code hangs here for ever. The CPU utilization also goes to 100% when the debugger reaches this line.

Answer 1

I just installed the visual web developer 2008 SP1 in the development server. Too bad that the data adapter.fill hangs in the debugger even in the development server. So it seems that the processor or memory is not causing this problem (as the development machine has enough of both of those). The configuration of the development server is below.

Development server configuration:

Dual Core AMD Opteron
Processor 280
2.39 GHz, 3 GB RAM

Visual Web Developer version: 2008 SP1
.NET Framework: 3.5 SP1
Start Options (Website ---> Start Options in VWD): .NET 2.0

So if anyone has faced similar problems, please let me know. This issue is totally stalling the development efforts :(.

Thanks in advance.

Answer 2

I have the exact same problem and have no good solution.  Have you found a solution yet?  It appears others have problems like this as well:

http://social.msdn.microsoft.com/Forums/en/csharpgeneral/thread/1350c0ac-7e83-41cc-8df8-11318e3c28ee

http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework.adonet/topic34540.aspx

http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/b1136a81-ea82-4364-bfb4-0614745b6070

My problem occurs both when running in the debugger and when running the the .exe standalone.  I've tried others recommendations from the aforementioned links to no avail.  Others seem to have success when compiling in x86 mode only (b/c the OLE provider can't handle 64bit).

This is extraordinarily frustrating that a simple DB access call is so difficult.

Answer 3

I have the exact same problem and have no good solution.  Have you found a solution yet?  It appears others have problems like this as well:

http://social.msdn.microsoft.com/Forums/en/csharpgeneral/thread/1350c0ac-7e83-41cc-8df8-11318e3c28ee

http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework.adonet/topic34540.aspx

http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/b1136a81-ea82-4364-bfb4-0614745b6070

My problem occurs both when running in the debugger and when running the the .exe standalone.  I've tried others recommendations from the aforementioned links to no avail.  Others seem to have success when compiling in x86 mode only (b/c the OLE provider can't handle 64bit).

This is extraordinrily frustrating that a simple DB access call is so difficult.

I have the similar question, Who can give an answer? I've been concerned about the issue,  It's long.