MySQL Forums :: Announcements :: MySQL Connector/J 5.1.24 has been released

Hello all,

MySQL Connector/J 5.1.24, a maintenance release of the production
5.1 branch has been released. Connector/J is the Type-IV pure-Java
JDBC driver for MySQL.

Version 5.1.24 is suitable for use with many MySQL server versions,
including 4.1, 5.0, 5.1, 5.4, 5.5 and 5.6.

It is now available in source and binary form from the Connector/J
download pages at
http://dev.mysql.com/downloads/connector/j/5.1.html
and mirror sites as well as Maven-2 repositories.

As always, we recommend that you check the "CHANGES" file in the
download archive to be aware of changes in behavior that might affect
your application.

MySQL Connector/J 5.1.24 includes the following general bug fixes
and improvements:

Changes in MySQL Connector/J 5.1.24 (2013-03-12)

   Bugs Fixed

     * The Statement.cancel() was made less susceptible to
       deadlocking, to allow application servers to immediately
       cancel operations that fail due to transaction timeouts or
       network issues. The abortInternal() method that was previously
       part of the MySQLConnection interface is now available through
       the Connection interface, so it can be tested for and called
       if available. (Bug #16224249)

     * When a statement was accessing a table in streaming mode,
       terminating the statement by issuing KILL QUERY from another
       session could cause a SQLException "Query execution was
       interrupted" and a stall when the original session issued a
       ResultSet.close() or Statement.close() method call. This issue
       resulted from a race condition and so could happen
       intermittently. (Bug #16198772, Bug #64204)

     * When the connection options noDatetimeStringSync and
       useTimezone were specified together, which is not allowed, the
       error message referred to an incorrect option name
       noDatetimeSync. (Bug #16061665, Bug #68011)

     * The connection.getQueryTimeoutKillsConnection() method could
       be called with a null parameter, causing NullPointerException
       errors and stack traces. The error depended on a race
       condition and so occurred intermittently. (Bug #13943631, Bug
       #64805)

Thanks,
On behalf of the MySQL/ORACLE Build Team

Murthy Narkedimilli