MySQL Connector/J 6.0.4 m3 Development Release has been released (no replies)

Dear MySQL users,

MySQL Connector/J 6.0.4 m3 Development Release is a developer milestone
release for the 6.0.x series.
This release includes the following new features and changes, also described
in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-6-0-4.html.

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.

To download MySQL Connector/J 6.0.4 M3, see the "Development
Releases" tab at http://dev.mysql.com/downloads/connector/j/


Enjoy!

   Changes in MySQL Connector/J 6.0.4 (2016-09-06, Milestone 3)

   Version 6.0.4 Milestone 3 is the third development release of
   the 6.0 branch of MySQL Connector/J, providing an insight
   into upcoming features. It is suitable for use with MySQL
   server versions 5.5, 5.6, and 5.7. It supports the Java
   Database Connectivity (JDBC) 4.2 API.

   Functionality Added or Changed

     * Connector/J now supports the shorthand notation "*" in
       SQL expressions (for example, SELECT COUNT(*) FROM
       mytable) for connections using the X Protocol. (Bug
       #21790242)

   Bugs Fixed

     * On Windows platforms, SSL connections to MySQL servers
       using the X Protocol hung. (Bug #24301468)

     * Connector/J could not be installed as an OSGi bundle,
       because in the Manifest of the Connector/J JAR file, the
       variable name for the OSGi version number was wrong. (Bug
       #23743947, Bug #82046)

     * When Connector/J tried to read from a column of the BIT
       (http://dev.mysql.com/doc/refman/5.7/en/bit-type.html)
       data type, an ArrayIndexOutOfBoundsException resulted.
       (Bug #23644816, Bug #81755, Bug #22931433)

     * A memory leakage occurred when the connection properties
       cachePrepStmts and useServerPrepStmts were both set to be
       true and server-side prepared statements were set as
       non-poolable, which resulted in the prepared statement
       being not closable by the client, and the number of
       prepared statements then kept on increasing.
       When the memory leakage described above occurred, it did
       not make Connector/J fail, as Connector/J switched to
       using client-side prepared statements when the maximum
       number of prepared statements was reached. However, when
       rewriteBatchedStatements was also set to true, the switch
       to client-side prepared statements did not occur, and
       Connector/J threw the MySQLSyntaxErrorException ("Can't
       create more than max_prepared_stmt_count statements")
       when the client wanted to create more prepared statements
       than allowed.
       This fix corrected the way prepared statements are
       handled in order to avoid both of the problems described
       above. (Bug #22954007, Bug #80615)

     * Connector/J failed to connect to a server when using a
       blank password. (Bug #21690043)

Documentation
--------------
Online: http://dev.mysql.com/doc/connector-j/6.0/en/index.html

Reporting Bugs
---------------
We welcome and appreciate your feedback and bug reports:
http://bugs.mysql.com/

On behalf of the MySQL Release Team
-Sreedhar S