The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-15. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB Connector/J 1.3.4 Release Notes

The most recent Stable (GA) release of MariaDB Connector/J is:
MariaDB Connector/J 3.5.0

Download Release Notes Changelog Connector/J Overview

Release date: 12 Jan 2016

MariaDB Connector/J 1.3.4 is a Stable (GA) release.

For a description of MariaDB Connector/J see the About MariaDB Connector/J page

For a list of all changes made in this release, with links to detailed information on each push, see the changelog.

This version is a bugfix release

Notable changes and additions

Major

  • Failover improvements (reconnection implementation evolution, thread handling ...)
  • CONJ-236 : Correction on using getInt on a signed smallInt negative value on prepareStatement
  • CONJ-238 : PrepareStatement prepare exception handling

Minor

  • CONJ-237 : Closing a close statement does not throw an Exception anymore
  • CONJ-239 : Permit commit when in autocommit mode
  • CONJ-240 : Permit using Connection.setReadOnly(true) during a transaction

Behavior change

On a master/slave cluster, the driver uses 2 underlying connections: one to a master instance, one to a slave instance. When one of the connections fails, if the driver needs it right away, it will create a new connection immediately before re-executing the query, if possible.

If the failed connection is not needed immediately, this driver will subscribe to the "failover reconnection" that will be handled in other threads. Failover threads will attempt to create a new connection to replace a failing one, so the interruption is minimal for the queries in progress. When the client asks to use a failed connection, the new connection created by the failover thread will replace the failed one.

Example: after a failure on a slave connection, readonly operations are temporary executed on the master connection to avoid interruption on the client side. The failover thread will then create a new slave connection that will replace the failed one. The next query will use the new slave connection.

A pool of threads is initialized when using a master/slave configuration. The pool size evolves according to the number of connections.

More information on GitHub here: high availability documentation

Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.

MariaDB may already be included in your favorite OS distribution. More information can be found on the Distributions which Include MariaDB page.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.