Bug #838 | all JDBC connections fail | ||
---|---|---|---|
Submitted: | 13 Jul 2003 13:10 | Modified: | 14 Jul 2003 6:33 |
Reporter: | Ronald Jeremy | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 4.1.1-alpha | OS: | Linux (redhat linux 8) |
Assigned to: | Mark Matthews | CPU Architecture: | Any |
[13 Jul 2003 13:10]
Ronald Jeremy
[14 Jul 2003 6:33]
Mark Matthews
MySQL-4.1.1 is not a _released_ version of MySQL...Notice that the age of both 3.0.8 and 3.1.0 (which both support 4.1.x) is _older_ than your build of MySQL-4.1. MySQL-4.1.1 is _alpha_ code and has _many_ changes in the protocol that Connector/J released versions don't know about (they couldn't as they were released before the changes were made). If you want to work with BK builds of MySQL, you will need to use a nightly snapshot of Connector/J (from http://mmmysql.sourceforge.net/snapshots/) to access anything newer than MySQL-4.1.0 (the released version). Regards, -Mark
[27 Nov 2003 6:42]
[ name withheld ]
I'm have the same problem, BUT I'm using mysql server 4.1.0-alpha and mysql-connector-java 3.0.9-stable. However, it is possible to connect with the same application and same JDBC driver to a mysql 4.0.12 database server... That make me think that the problem is in mysql server > 4.1.0 I have also tried this with mysql-connector-java-3.1.0-alpha. Please also refer to this discussion where Mr. Mark Matthews at MySQL AB replies that 4.1.0 has some buggy auth code: http://dbforums.com/arch/174/2003/8/897454
[27 Nov 2003 6:52]
[ name withheld ]
Hmm, I just now tested it with mysql-connector-java-3.1-nightly-20031127 (db=4.1.0-alpha) and got the same result again. My OS is RedHat 7.2 if that matters. (A friend of mine claims that it works fine on windows - I havent tested.)
[27 Nov 2003 7:25]
[ name withheld ]
Now I tested it on my own windows-box and that worked fine! Then I made a fresh installation of mysql 4.1.0-alpha on another linux-box (redhat 7.3) which also worked fine. I must say that it is probably my installation of mysql that is not doing very well (alternatively redhat 7.2). Sorry for bugging you busy guys whit this nonsense ;-(