http://bugs.mysql.com/bug.php?id=21913 I'm stuck since it appears 4.1.20 has been removed from portage, and the fix was pushed to 4.1.22.. Seems that even if I migrate to 5.0 the bug will still persist until 5.0.25. will try rolling back the connector
What's mysql-connector-j? Which ebuild does install this?
(In reply to comment #1) > What's mysql-connector-j? Which ebuild does install this? > well, in portage i guess the package is "jdbc-mysql" which is at version 3.1.10, but the latest stable from mysql is 3.1.13 (avaialble http://dev.mysql.com/downloads/connector/j/3.1.html) the connector is used to provide communication with mysql for java/servlet apps
Hmmm...
confirmed connector 3.1.10 IS working
The latest version in the tree is 3.1.13, please see if that helps the problem.
Well the bug is about 3.1.13. But it was originally installed by hand by the reporter because he didn't see it was already in portage, just ~arch? You shouldn't fill bugs for gentoo about stuff you didn't install from portage... In any case, upstream bug suggests the problem is in the server, not in the connector, so rolling back to 3.1.10 is just workaround, not solution. So we either wait for upstream's fixed release or apply the patches now and revbump (Jon, you could test that in your local overlay :)
According to upstream bug, this is fixed in mysql >=4.1.22, >=5.0.25 and >=5.1.12. We have 4.1.22-r1 and 5.0.26-r2 stable, 5.1.x has never been stable anywhere => closing FIXED.
