Jon Miles wrote:
> I'm getting exactly the same error with Mysql
> 4.1.13, we have tried out Connector/J 3.1.10,
> 3.2.0 alpha, and 3.0.8 stable, and all get this
> error. What can I do? Is there some particular
> version of the connector that WORKS for this?
>
> Other things I have tried and have not worked:
> - Switched passwords on the Mysql server to the
> old encryption type using OLD_PASSWORD.
> - Set grant accesses of all kinds on my main
> database user, finally settling back to giving it
> ALL PRIVILEGES on its database.
>
> None of these work. I can use the mysql client
> from a 4.0.21 Mysql install and connect to it
> perfectly. I can use DBI from perl to connect to
> it with no trouble, but the Connector/J never
> works.
>
> Why did this work at one point (4.1.11 and 3.2.0
> alpha) and NOT work now? How can I fix this? Our
> production DB is worthless if we can't connect to
> it.
>
> Jon Miles
You're using an ALPHA driver on your production server?
Any way, this only ever happens if you have a version of the driver sitting in your classpath that doesn't understand a newer server. I'd _really_, _really_ look for a mysql-connector-java* on your filesystem that isn't where you expect...
-Mark
Mark Matthews
Consulting Member Technical Staff - MySQL Enterprise Tools
Oracle
http://www.mysql.com/products/enterprise/monitor.html