Dear MySQL Users,

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

MySQL Connector Java is available in source and binary form from the
Connector/J download pages at
and mirror sites as well as Maven-2 repositories.

MySQL Connector Java (Commercial) is already 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.43 includes the following general bug fixes and
improvements, also available in more detail on

Changes in MySQL Connector/J 5.1.43 (2017-07-21)

   Version 5.1.43 is a maintenance release of the production 5.1
   branch. 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

     * Update the time zone mappings using the latest IANA and
       CLDR time zone databases. (Bug #25946965)

     * A new option for the loadBalancingStrategy connection
       property called serverAffinity has been added. The
       servers listed in the new connection property
       serverAffinityOrder (which should be a subset of the
       servers in the host list of the connection URL) are
       contacted in the order they are listed until a server is
       available or until the list of servers is exhausted, at
       which point a random load-balancing strategy is used with
       the hosts not listed by serverAffinityOrder. See
       descriptions for loadBalancingStrategy and
       serverAffinityOrder in Driver/Datasource Class Names, URL
       Syntax and Configuration Properties for Connector/J

       for details. (Bug #20182108)

   Bugs Fixed

     * Secure JDBC connections did not fall back to the default
       truststore when a custom one was not provided. (Bug

     * Connector/J failed a number of regression tests in the
       testsuite related to geographic information system (GIS)
       functions because of changes to GIS support by the MySQL
       server. The fix corrects the tests. (Bug #26239946, Bug

     * Attempts to connect to a server started with collation
       utf8mb4_de_pb_0900_ai_ci resulted in null pointer
       exceptions. (Bug #26090721)

     * In com/mysql/jdbc/, the
       arguments resultSetType and resultSetConcurrency for a
       call of Connection.preparedStatement() were swapped. (Bug
       #25874048, Bug #85885)

     * A NullPointerException was returned when getDate(),
       getTime(), or getTimestamp() was called with a null
       Calendar. This fix makes Connector/J throw an
       SQLException in the case. (Bug #25650305)

     * Some JDBC proxied objects were missing the proper
       handling of the equals() methods, thus even comparison of
       one of these proxied objects to its own self with
       equals() yielded false. This patch introduces proper
       handling for the equals() method in all the relevant
       proxies. (Bug #21931572, Bug #78313)

     * A server-side prepared statement was not closed when the
       same statement was being prepared again while the
       original statement was being cached. This was caused by
       the silent replacement of the cache entry of the old
       statement by the new. When this happened repeatedly, it
       caused eventually the complaint that
       max_prepared_stmt_count was exceeded. This fix makes sure
       that when a cache entry for a statement replaces an older
       one, the older statement is immediately closed. (Bug
       #20066806, Bug #74932)

On Behalf of the MySQL/Oracle Release Engineering Team,
Hery Ramilison

MySQL General Mailing List
For list archives:
To unsubscribe:

Reply via email to