MySQL Bugs: #25953: ASP.NET page returns "object reference not set" when update is attempted

Bug #25953	ASP.NET page returns "object reference not set" when update is attempted
Submitted:	30 Jan 2007 16:50	Modified:	12 Apr 2007 18:18
Reporter:	[ name withheld ]	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	5.0.3	OS:	Any (Server 2003)
Assigned to:		CPU Architecture:	Any
Tags:	exception ASP.NET object reference

Description:
I have a very puzzling error that I can't exactly nail down, but am pretty sure it isn't the code on the ASP.NET page, because (A) It's a very simple page and (B) My current workaround is to reboot the web server when it happens. It also doesn't appear to be the MySQL server itself, because I can still issue UPDATE and INSERT commands via the phpMyAdmin interface for the MySQL server just fine. It doesn't appear to be a networking problem between the database and web server, because they can still "see" each other via a simple ping. 

This only appears to happen when several hours pass and the ASP.NET site isn't requested by any clients (such as overnight or over the weekend).

How to repeat:
Issue an INSERT or UPDATE command to a MySQL server from an ASP.NET page. The two servers should be running on physically different machines.

Suggested fix:
I'm not sure - perhaps managing the connection state a little better?

Problem is still occurring.

What connection string are you using?  If you are not disabling connection pooling and including "connection reset=false" on  your connection string, then that will cause the problem.  We have committed a fix for this to our source repo.  The work around until 5.0.4 is released is to either diable pooling or set 'connection reset=true' on your connection string.

Hi. You provided no feedback regarding Reggies suggestions...

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".