I wondered whether you managed to solve this? If so, could you share
with us what you did?
I have a program which processes all transaction in a table, then sleeps
for a period before trying again. This program always crashed with the
error you describe after it had processed around a 100 or so records.
This was with the Connector/Net 1.0.4. I changed to using the ODBC 3.51
driver and now it can handle several hundred (or even a thousand)
records before crashing. Problem is that I need it to handle 10 000 records.
Any ideas on how to track down what might be causing this? I have tried
running it both against a local server and a remote one, both are MySql
Not wanting to start any flames, but I think that the ODBC is still
quite a bit faster than the 1.0.4 Connector/Net to handle 1 read from
the table then 2 table inserts and 5 table updates.
James Moore said the following wise words on 2005-02-13 19:43:
>Been chasing this for a while with no success, so I thought I'd see if
>anyone has any thoughts. Next thing on my list is to try it using an ODBC
>Connector 1.0.4 talking to 4.1.9 server; server is running on a redhat 7.3
>box. Haven't installed 4.1.X server on the windows side, but was seeing the
>same issue when talking to a 4.0.21 server running on the same machine as
>the .Net app.
>My application runs fine for an hour or so, happily reading and writing to
>the database, until I finally get a System.IO.IOException.