MySQL Connector/J 5.1.38 has been released (no replies)

Hello all,

MySQL Connector Java 5.1.38, a maintenance release of the production 5.1
branch, has been released. Connector/J is a Type-IV pure-Java JDBC
driver for MySQL. It is suitable for use with MySQL server versions 5.5,
5.6, and 5.7. It is also the first release of MySQL Connector/J to support
the Java Database Connectivity (JDBC) 4.2 API.

MySQL Connector Java is available in source and binary form from the
Connector/J download pages at
http://dev.mysql.com/downloads/connector/j/5.1.html

MySQL Connector Java (Commercial) is available for download on the My
Oracle Support (MOS) website. This release will be available on
eDelivery (OSDC) in next month's upload cycle.

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.38 includes the following general bug fixes and
improvements, also available in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-38.html :

Changes in MySQL Connector/J 5.1.38 (2015-12-07)

   Functionality Added or Changed

     * When connecting to a MySQL server 5.7 instance that
       supports TLS, Connector/J now prefers a TLS over a plain
       TCP connection. (Bug #21947042)

     * Two new connection properties, allowSlaveDownConnections
       and readFromMasterWhenNoSlaves, have been introduced for
       configuring replication-aware connections. See
       Configuring Master/Slave Replication with Connector/J
       (http://dev.mysql.com/doc/connector-j/en/connector-j-master-slave-replication-connection.html)
       and the entries for the new properties in Driver/Datasource
       Class Names, URL Syntax and Configuration Properties for
       Connector/J (http://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html)
       for details. (Bug #21286268)

   Bugs Fixed

     * In a Fabric environment, a ClassCastException resulted
       when a stored procedure was called with an INOUT
       parameter. This was because in this situation, what was
       being cast was a proxied version of the object. This fix
       extracts the underlying object from its proxy, allowing
       it to be cast to the implementing class. (Bug #22096981)

     * getTypeInfo() erroneously returned a PRECISION value of
       "255" instead of "65535" for the data type VARBINARY.
       (Bug #21978216)

     * A deadlock was observed when in the same server group,
       two concurrent threads were using different Fabric
       connections, and one executed a failover procedure while
       the other simultaneously called a method that acquired a
       lock on the underlying replication connection instance
       monitor. This fix revised the locking mechanism of
       replication connections, in order to prevent the observed
       deadlocks. (Bug #21966391, Bug #21934573, Bug #78710)

     * State information of a Fabric group was not updated by
       Connector/J after a local cache's Time to Live (TTL)
       expired, which resulted in the client not recognizing any
       topology changes happening to the group like a master
       failover, a server rejoining, and so on. (Bug #21296840,
       Bug #17910835)

     * Connector/J threw an AbstractMethodError when a JDBC 4
       functionality (for example, createBlob()) was used on a
       replication-aware connection. This has been fixed by
       putting replication connections under the multi-host
       connection proxy structure that Connector/J has been
       using for load-balanced and fail-over connections. (Bug
       #11763419)
       References: See also Bug #11763401.

     * After the initial call of Connection.setReadOnly()
       following the creation of a replication-aware connection,
       subsequent calls of Connection.setReadOnly() could not
       change the nature of the connection. This has been fixed
       by putting replication connections under the multi-host
       connection proxy structure that Connector/J has been
       using for load-balanced and fail-over connections. (Bug
       #11763401)
       References: See also Bug #11763419.

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

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

On Behalf of the MySQL/ORACLE RE Team
Hery Ramilison