Devart Forums

I am getting an exception when setting TMyStoredProc.StoredProcName at runtime in a web application. The message returned is:

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


The procedure exists, and when starting a new GUI application to test this behavior, I cannot duplicate the error with components on form. It fetches perfectly as well.

I am using MyDAC version 4.30.0.11 over TCP connection and my version of MySQL is 5.0.18-nt

Possibly you try using one MyConnection for different threads in the multithreaded application. You should know that one MyConnection object per thread is required.

Antaeus wrote:Possibly you try using one MyConnection for different threads in the multithreaded application. You should know that one MyConnection object per thread is required.

I am following this rule. It is a multi-threaded application, but this behavior is within the same thread. Prior to this exception, I am opening another stored procedure, fetching, closing and destroying the stored proc object with no errors. Then, I create a new stored procedure object, set the StoredProcName and encounter this exception.

Lastly, last night I tried disconnecting after first stored procedure fetching, then reconnecting to MySQL and had no errors. But this takes additional time, to disconnect and reconnect. There is latentcy with connecting. I want to keep connection open. Have multiple stored procedures to open for one "hit".

Something else must be causing the problem. In another large database web application I am doing the same type of thing in many places. Within one "hit" I am opening up to 10 procedures. That database is far more complex and has much more data to retrieve.

What else should I be looking at? Could the problem somehow be related to MySQL itself? Or is this behavior limited to MyDAC?

Thanks for any help!

This problem looks like the one discussed in this topic. If you think that the problem you have come across differs from it, then make please simple example that shows the problem and send it to us (evgeniyD*crlab*com).