MySQL Connector/J 5.1.36 has been released
Hello all, MySQL Connector/J 5.1.36, 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 and 5.6. 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.36 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-36.html : Changes in MySQL Connector/J 5.1.36 (2015-07-02) Version 5.1.36 is a maintenance release of the production 5.1 branch. It is suitable for use with MySQL server versions 5.5, and 5.6. Functionality Added or Changed * The files in the Maven Central Repository for each Connector/J release have been reorganized and a source artifact (*-sources.jar) has been added, for release 5.1.21 and after. (Bug #20283655, Bug #75335) Bugs Fixed * Results returned by DatabaseMetaData.getCatalogs() were not properly sorted by catalog name. (Bug #21215151) * A ClassCastException occurred when Connector/J was executing a streaming prepared statement in a Fabric environment. (Bug #21184949, Bug #77217) * Connector/J did not use the character set specified with the connection property passwordCharacterEncoding for authentication. With this fix, the property is now honored. If it is not set, Connector/J uses the value of characterEncoding instead; if even that is not set, Conenctor/J defaults to UTF-8 for the password's encoding. (Bug #20825727) * A failover did not occur for a MySQL Fabric connection during the failure of a master server. It was because the state change of the Fabric connection group was not handled properly, which hs been corrected by this fix. (Bug #20821888, Bug #75113) * When the getDate() and getTime() methods of ResultSet were called to retrieve values with fractional seconds, a bad format error occurred. With this fix, the fractional seconds are dropped before the retrieved values are converted into a Date or Time object. (Bug #20804635) * A StringIndexOutOfBoundsException occurred when getProcedureColumns() were trying to return ENUM or SET type procedures or functions that involved reserved words. That was caused by a problem in the parser for the functions' or procedures' CREATE statements, which this fix corrects. (Bug #20727196) * At every connection, Connector/J executed a SHOW VARIABLES WHERE statement over a multitude of variables, which consumed a lot of time and memory. To improve the efficiency of the code, this fix replaces the statement with the more efficient SELECT @@variable query and also implements some other related changes. (Bug #20408891, Bug #75592) * getProcedures(), getFunctions(), getProcedureColumns(), and getFunctionColumns() returned duplicate results when the connection parameter nullCatalogMeansCurrent was set to false. (Bug #19803348) * An UnsupportedEncodingException during handshake gave rise to a NullPointerException. With this fix, the NullPointerException is no longer thrown, and a proper error message is provided by Connector/J. (Bug #18758686, Bug #72630) * When using Connector/J with MySQL Fabric, the createGroup() method failed with a ClassCastException. (Bug #18719760, Bug #72546) * Using Connector/J to connect with non-null user name and password to a MySQL Fabric server that had authentication disabled resulted in a NullPointerException. (Bug #18425861, Bug #72077) * The change user functionality in Connector/J was dependent on Bug# 70865 of the MySQL server (for releases 5.5 and later, the server unnecessarily sends a plugin_request_packet for every COM_CHANGE_USER packet). That dependence made the com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSour ce interface fail for server versions or forks that did not have the same bug. This fix removes that dependence and makes the interface function properly, whether the server suffers Bug# 70865 or not. (Bug #17810800, Bug #70927) * JDBC4MySQLPooledConnection keeps a list of statementEventListener instances named statementEventListeners, which is used as monitor lock whenever the fireStatementEvent() method is called. However, because the pooled connection's close() method set statementEventListener to be null, if a prepared statement was closed
Unable to start mysql after power Failure
Hi All We are trying to High Availability solution for our database. We have our application running on a node-1 and the DB running on the shared storage which is shared across node-1 node-2. Whenever there is a power Failure on node-1 , we start our application on node-2 but our problem is that now after a failover onto node-2 the DB deamon on node-2 will fail to start. Mysql version information: ** Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 58 Server version: 5.6.10-enterprise-commercial-advanced MySQL Enterprise Server - Advanced Edition (Commercial) Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql *** On the node-2 when the DB deamon tries to start we are seeing the following error messages in the log file: Error Message * 150703 16:01:11 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/data 2015-07-03 16:01:11 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-07-03 16:01:11 16278 [Note] Plugin 'FEDERATED' is disabled. 2015-07-03 16:01:12 16278 [Note] InnoDB: The InnoDB memory heap is disabled 2015-07-03 16:01:12 16278 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-07-03 16:01:12 16278 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-07-03 16:01:12 16278 [Note] InnoDB: CPU does not support crc32 instructions 2015-07-03 16:01:12 16278 [Note] InnoDB: Using Linux native AIO 2015-07-03 16:01:12 16278 [Note] InnoDB: Initializing buffer pool, size = 1.0G 2015-07-03 16:01:12 16278 [Note] InnoDB: Completed initialization of buffer pool 2015-07-03 16:01:12 16278 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11 2015-07-03 16:01:12 16278 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2015-07-03 16:01:12 16278 [Note] InnoDB: Retrying to lock the first data file 2015-07-03 16:01:13 16278 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11 2015-07-03 16:01:13 16278 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2015-07-03 16:01:14 16278 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11 2015-07-03 16:01:14 16278 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2015-07-03 16:01:15 16278 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11 2015-07-03 16:02:52 16278 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2015-07-03 16:02:52 16278 [Note] InnoDB: Unable to open the first data file 2015-07-03 16:02:52 7f9b9194e720 InnoDB: Operating system error number 11 in a file operation. InnoDB: Error number 11 means 'Resource temporarily unavailable'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2015-07-03 16:02:52 16278 [ERROR] InnoDB: Can't open './ibdata1' 2015-07-03 16:02:52 16278 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! 2015-07-03 16:02:52 16278 [ERROR] Plugin 'InnoDB' init function returned error. 2015-07-03 16:02:52 16278 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2015-07-03 16:02:52 16278 [ERROR] Unknown/unsupported storage engine: InnoDB 2015-07-03 16:02:52 16278 [ERROR] Aborting 2015-07-03 16:02:52 16278 [Note] Binlog end 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'partition' 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'ARCHIVE' 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'BLACKHOLE' 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2015-07-03 16:02:52 16278 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2015-07-03 16:02:52 16278
