I'm running into this problem where my database connection seems to
get disconnected by something unknown to me. My server is running
locally so any network problems shouldn't have any affect on my
connection. I'm not sure if it's time based or due to some other
external event. So far my tests to leave an open (idle) connection for
an extended period of time haven't reproduced this error.
The exceptions look something like this and track back to my original
execute statement:
Unable to write data to the transport connection. --->
System.IO.IOException: Unable to write data to the transport
connection. ---System.Net.Sockets.SocketException: An established
connection was aborted by the software in your host machine at
System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size,
SocketFlags socketFlags) at
System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset,
Int32 size)
I haven't found a connection timeout type parameter that would cause
this behavior - only the connection timeout property on the
connection object which is only for actually making the conection. I
checked the lifetime services of the .NET connector for the
MySqlConnection() object and it's null so it should have an infinite
lifetime.
I haven't seen anything in the server log (which never seems to have
anything useful - just startup and shutdown). I haven't seen any
other related exceptions so I'm not sure what is going on here.
Testing for this exception and attempting to re-connect is really
unacceptable solution. I also don't want to start a new connection
every time because there are times when there are bursts of writes and
queries from multiple connections on multiple threads (one thread per
connection).
I'm using:
MySQL 4.1.10
MySQL .NET Connector 1.0.4
