Strange trouble with ADO.NET

bunnyhopper · January 15th, 2007, 02:40 PM

Hi forum members,

I developed a ASP.NET application (a Content Management System) that is online by now. It can be used by around 500 registered users at the same time. There is a feature I implemented which sends me automatic error messages (via e-mail) whenever an error occurs in the application (while a user is working).

Unfortunately I keep getting these strange error messages each having something to do with ADO.NET (I'm running SQL-Server 2000 on a seperate database server).

This is one of the strange error I'm getting:

Code:

SqlCommand-Object: (CommandText=member_select_PrivilegesById)(CommandType=StoredProcedure)(Connection=server=192.168.100.20; uid=bikenet;database=bikenet; Connection Timeout=60; Min Pool Size=10; Max Pool Size=2000)

SqlDataAdapter-Object: (SelectCommand<>null)


Object reference not set to an instance of an object.   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
   at index_red.DB_Abfrage.ReturnDataTable() in c:\inetpub\wwwroot\index_red\db_abfrage.cs:line 108
   at index_red.DB_Abfrage.ReturnDataTable() in c:\inetpub\wwwroot\index_red\db_abfrage.cs:line 116
   at index_red.UserFuncs.GetUserMode(Int32 member_id) in c:\inetpub\wwwroot\index_red\auxiliaries.cs:line 293
   at index_red.UserFuncs.GetBaseFile(HttpSessionState Session) in c:\inetpub\wwwroot\index_red\auxiliaries.cs:line 333
   at index_red.sa_gebraucht_main.lbtnListe_Click(Object sender, EventArgs e) in C:\Inetpub\wwwroot\index_red\sa_gebraucht_main.ascx.cs:line 105
   at System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e)
   at System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain()

The first few lines are inserted by the error handling method just to make sure everything is fine. However my SqlCommand-Object seems to be valid (with a valid connection). Something goes wrong with the SqlDataAdapter.

Another error message I sometimes get is:

Code:

Internal connection fatal error.   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)

or

Code:

Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
   at System.Data.SqlClient.SqlDataReader.InternalClose(Boolean closeReader)
   at System.Data.SqlClient.SqlDataReader.Close()
   at System.Data.SqlClient.SqlConnection.CloseReader()
   at System.Data.SqlClient.SqlConnection.Close()

These error happen around 10 to 20 times a day randomly for random users. I have no idea what's wrong. I can post my database class if you need it.

Regards,

Krisztian

bunnyhopper · January 16th, 2007, 04:55 AM

Ok, I think that the problem must lie within my DB routine class.

The class is using static methods and static members and I used to call it like this:

Code:

DB_Abfrage.InitializeSPCall("bbs_berichte_bloecke_select_insert_update_delete_EntryById");

Code:

            DB_Abfrage.AddParameter("@operation", "insert");
            DB_Abfrage.AddParameter("@bbs_berichte_id", int.Parse(bbs_berichte_id));
            DB_Abfrage.AddParameter("@bbs_blocktype", bbs_blocktype);
            DB_Abfrage.InsertUpdateDeleteQuery(true);

But than I read this on a site:

The Web server does not run a separate copy of your application for each user accessing your web site. Bear this in mind as you read through the rest of this article, because you don't want to code global static variables as if each user has a separate copy of them. For per-user data, use session variables instead. For information on session variables, search the MSDN online help for HttpSessionState. Even though there are multiple HttpApplication instances, there's still no guarantee which of these are shared among which users. Each user accessing the site does not necessarily get his own instance of HttpApplication.

So my question is. Could it be that when the class accesses a static member, the static member is not the same as before or that other users access the same static member and corrupt the data stored in it? Does it make sense to use static member in a class (with ASP.NET) at all?

Until now I rewrote the entire DB class and now it is using session variables instead. I hope this was the problem.

woodyz · January 16th, 2007, 12:02 PM

You might be on to something. Using static members makes sence in an ASP.NET application, but of course - only when appropriate.

If you are using static members as if they are private to one particular session or user, then it will certainly cause you problems. A static member is visible to all instances of the class (or all other code that has access to the class when the member's scope allows it).

Woody Z
http://www.learntoprogramnow.com

bunnyhopper · January 16th, 2007, 12:54 PM

Why would it make sense to use a static member than? If it's shared among other users but not all of them. All I can think of is a constant static member.