MySQL Connector/J 5.1.25 has been released
Posted by: Jocelyn Ramilison
Date: May 06, 2013 10:30AM
Date: May 06, 2013 10:30AM
Hello all, MySQL Connector/J 5.1.25, 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.25 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.25 includes the following general bug fixes and improvements, also listed in more detail on http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-25.html Changes in MySQL Connector/J 5.1.25 (01 May 2013) Bugs Fixed * The getDriverName() function would return "MySQL-AB JDBC Driver" as the driver name. This fix changes the driver name string to "MySQL Connector Java". (Bug #16436511) * An exception occurred if NULL was passed to a stored procedure INOUT parameter. (Bug #60816, Bug #12800874) * The "mysql-connector-java-5.1.24.jar" prepared for maven.org contained the artifact, META-INF/INDEX.LIST, which incorrectly pointed to "mysql-connector-java-5.1.24-bin.jar". For Connector/J 5.1.25, META-INF/INDEX.LIST has been corrected and now points to "mysql-connector-java-5.1.25.jar". The work around for "mysql-connector-java-5.1.24.jar" prepared for maven.org is to rename the JAR file to "mysql-connector-java-5.1.24-bin.jar" or to download the MySQL Connector/J 5.1.24 driver from http://dev.mysql.com/downloads/connector/j/. (Bug #68801, Bug #16574419) * ReplicationConnection.isMasterConnection(), which is intended to check if the current connection is the master connection, would always return "false". This fix implements logic that returns "true" if the current connection is the master connection. (Bug #68763, Bug #16545334) * When using Connector/J in a replication deployment, all of the slave connections would not be pinged. This fix ensures that all active physical connections to slaves are pinged, and that communication exceptions are thrown if: + The master connection ping fails, and the connection is currently set to use the master connection via Connection.setReadOnly(false). + The Connection object is set to use the slave via Connection.setReadOnly(true), and the currently-selected slave connection ping fails. (Bug #68733, Bug #16526938) * Tomcat would fail to stop abandoned connection cleanup threads. The fix for Bug#65909 introduced the ability to stop daemon threads started by the Connector/J driver but it also cleared references from daemon threads to the parent classloader. When the clearReferencesStopThreads property is set to "true" in context.xml, Tomcat analyzes classloaders to detect and stop lost threads. This fix ensures that abandoned connection cleanup threads retain a reference to the parent classloader. (Bug #68556, Bug #16443387) * Producing Connector/J JAR packages in Eclipse using Ant tasks would result in a JAR file without compiled class files. Compile-related tasks in the Ant script would direct compilation targets to the bin directory (for Eclipse compatibility), while JAR related tasks were directed to {buildDir}/${fullProdName}. This fix changes the JAR task reference to ${compiler.output} instead of {buildDir}/${fullProdName}. (Bug #68664, Bug #16486957) * When connecting to a MySQL 5.6 server, Connector Java will now send connection attributes which are exposed in relevant PERFORMANCE_SCHEMA tables. By default, the following attributes are sent: _client_version: version number of MySQL Connector Java _client_name: "MySQL Connector Java" _client_license: "commercial" or "GPL", depending on the build used _runtime_vendor: JVM vendor name _runtime_version: JVM version The default attributes may also be augmented with user-defined key/value pairs, specified in the new connectionAttributes property (ex: connectionAttributes=key1:val1,key2:val2). The default attributes may also be suppressed entirely by setting connectionAttributes property to "none". Thanks, On behalf of the MySQL/ORACLE Build Team Hery Ramilison
Subject
Views
Written By
Posted
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.