MySQL Connector/J 5.1.25 has been released, and is available in Community and Enterprise flavors on dev.mysql.com and My Oracle Support, respectively. I’ve already noted the addition of support for connection attributes for MySQL 5.6 – 5.1.25 adds this functionality. This release also includes a fix for Bug#68733, which caused the special light-weight ping operation to execute only against the master and currently-selected slave, rather than the master plus all active slave connections. The ping operation exists to help ensure connections aren’t left idle for excessive durations in the internal load-balancing and replication “pools”, so failure to ping *all* active slave connections will make CommunicationFailureExceptions more likely after a rebalance operation selects a non-active, long-idle physical connection. This bug was found by Dominic Tootell and reported via the community forums in a wonderfully-researched post. It’s a great example of the type of community feedback and interaction that helps improve MySQL quality – thanks for the great contribution, Dominic!
In working through the bug Dominic reported, I found a couple other small bugs to fix. The first is Bug#68763, which caused ReplicationConnection.isMasterConnection() to incorrectly always report false. The second (Bug#68664) was an Ant build script bug which caused builds in Eclipse to produce a .JAR file – but it contained no .class files. Our standard builds are done from the Ant script rather than Eclipse, and I’ve typically worked around it by running Ant from the command-line when I needed to package (compiling has worked in Eclipse for some time thanks to Mark Matthews, just not packaging). Now you can package a .JAR file without leaving Eclipse. In another bug report, Alex Soklakov fixed Bug#68801, making Connector/J play nicely with Maven.
I hope you enjoy Connector/J 5.1.25!