Net packets out of order

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
jschnittger
Posts: 4
Joined: Tue 01 Aug 2006 14:42
Location: Ireland

Net packets out of order

Post by jschnittger » Tue 01 Aug 2006 15:02

Version: MySQLDirect.Net 2.80
MySQL Version: 4.1.* and 5.0 (Current general release)
Operating Systems: Windows XP and Fedore Core 3

We recieve the following errors using MySQLDirect when performing SELECT statements.

Code: Select all

Net packets out of order: received[110], expected[1]
Net packets out of order: received[58], expected[1]
Net packets out of order: received[32], expected[1]
Net packets out of order: received[110], expected[1]
Net packets out of order: received[115], expected[1]
I have seen this error several times on the forums, and came across the following post
Oleg wrote:Dear users,

New build of MySQLDirect .NET version 2.70.4.0 is available for download now.
This version includes:

* Bug with stored procedure describing fixed
* Bug with "Net packets out of order" fixed
* Bug with uppercase identifiers in MySqlCommandBuilder fixed

Core Lab development team
http://www.crlab.com/mysqlnet
Could you please provide information on how to prevent this issue or a definitive fix. If necessary we will upgrade to 3.5, however this is not preferable as we have a large install base.

Thanks,

/J

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Wed 02 Aug 2006 10:32

We had been working on this problem until version 3.20. So upgrading to 3.5, i suppose, is the best way to bring this error to nothing.

jschnittger
Posts: 4
Joined: Tue 01 Aug 2006 14:42
Location: Ireland

Post by jschnittger » Wed 02 Aug 2006 10:37

Does version 3.50 fix this problem? If it does not, and we still experience the problem is there any further information you can provide on the issue?

Thanks,

/J

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Wed 02 Aug 2006 10:56

Yes, this problem is fixed in version 3.50.

jschnittger
Posts: 4
Joined: Tue 01 Aug 2006 14:42
Location: Ireland

Post by jschnittger » Wed 02 Aug 2006 10:58

Thanks Alexey. We will download and test 3.50 now.

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Wed 02 Aug 2006 11:05

OK, we are looking forward to your comments.

jschnittger
Posts: 4
Joined: Tue 01 Aug 2006 14:42
Location: Ireland

Post by jschnittger » Wed 02 Aug 2006 13:16

Hi Alexey,

We have downloaded 3.50.11 (downloaded 2/8/2006), and we are still experiencing the problem:

Code: Select all

Exception filling dataset with SELECT ID from NS_Machines WHERE Target = 'DOMAIN\LAPTOP' : Net packets out of order: received[2], expected[1]
Net packets out of order: received[73], expected[1]

Error while executing : INSERT INTO NS_Machines(ID, Target, TargetTypeID, LastSeen) VALUES (0,'DOMAIN\NN-LAPTOP',3,'2006-08-02 14:07:14')

Net packets out of order: received[0], expected[1]

Exception filling dataset with SELECT ID from NS_Machines WHERE Target = 'DOMAIN\LAPTOP' : Net packets out of order: received[0], expected[1]

Exception filling dataset with SELECT COUNT(r.ID) FROM FS_Results r INNER JOIN NS_Machines m ON r.MachineID = m.ID INNER JOIN FS_Scans s ON r.ScanID = s.ID WHERE Target = 'DOMAIN\LAPTOP' AND ScannerID = '8FAFD8F7B6E88D1A7AF56A72E5EC666D' AND Error = 'N' : Net packets out of order: received[0], expected[1]
This is however happening under heavy use of the database, although it would still not be considered massive.

Could you please provide some information on how this problem has been fixed in the past?

Additional information:

Code: Select all

Net packets out of order: received[2], expected[1]

Exception filling dataset with SELECT ID from NS_Machines WHERE Target = 'DOMAIN\QA-TEST' : Invalid field length byte.
Thanks,

/J

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 03 Aug 2006 06:56

1. Make sure you close all data readers explicitly.
2. If you use Prepare() method of MySqlCommand class, call Dispose() after closing reader.
3. If you use connection pooling, call MySqlConnection.Ping() method before MySqlConnection.Open().
4. If above doesn't help and you use connection pooling, check if you can turn connection pooling off.

Please inform us whether our instructions helped you and which one solved the problem.

Post Reply