Re: Connector/J "Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost."

[Mark Matthews]

Andrew,

We've never been able to reproduce this problem internally, and when folks have solved it, it's either been a case of *their* application running out of resources, *their* network being flakey (not possible in your case), or *their* kernel having flakey networking (might be possible in your case, even with loopback connections). Thus the reason that it is "re-occurring" and "not being solved" is because in nearly all cases that I can remember it was something specific to the users' environment, and in the end not anything to do with the MySQL server or the JDBC driver.

Are you using MySQL from .debs? We have seen in the *past* issues with the way the MySQL server was built (compiler flags, and mix of gcc and glibc versions), which lead to things like server-side prepared statements not working correctly.

If you are using .debs, could you try using an "official" binary from MySQL to see if the issue goes away?

As you can see, there's lots of *potential* reasons this could happen, and many of the issues have nothing to do with the "stability" of the JDBC driver, and without more information than "This doesn't work for me", it's going to be awfully hard to track down just what *is* happening.

-Mark

Mark Matthews
Consulting Member Technical Staff - MySQL Enterprise Tools
Oracle
http://www.mysql.com/products/enterprise/monitor.html