Download | Release Notes | Changelog |
Release date: 7 Sep 2018
MariaDB Connector/J 2.3.0 is a Stable (GA) release.
MariaDB has now 2 new options to permit identifying deadlock : New options:
previous default value was "TLSv1, TLSv1.1", disabling TLSv1.2 by default, due to a corrected issue () with servers using YaSSL - not openSSL. Server error was . Now, the default value is "TLSv1, TLSv1.1, TLSv1.2". So TLSv1.2 can be use directly. Connecting MySQL community server use YaSSL without correction, and connection might result in SSLException: "Unsupported record version Unknown-0.0".
Using useBulkStmts permit faster batch, but cause one major issue : Batch return -1 = SUCCESS_NO_INFO
Different option use this information for optimistic update, and cannot confirm if update succeed or not. This option still makes sense, since for big batch is way more faster, but will not be activated by default.
[] optimization to read metadata faster
[] java.sql.Driver class implement DriverPropertyInfo[] getPropertyInfo, permitting listing options on querying tools
[] enabledSslProtocolSuites does not include TLSv1.2 by default
[] update maven test dependencies for java 10 compatibility
[] correction on possible NPE on getConnection when using failover configuration and master is down, not throwing a proper exception
[] Error in batch might throw a NPE and not the proper Exception
[CONJ-643] PreparedStatement::getParameterMetaData always returns VARSTRING as type resulting in downstream libraries interpreting values wrongly
includeInnodbStatusInDeadlockExceptions
add "SHOW ENGINE INNODB STATUS" result to exception trace when having a deadlock exception.Default: false
includeThreadDumpInDeadlockExceptions
add thread dump to exception trace when having a deadlock exception.Default: false
This page is: Copyright © 2025 MariaDB. All rights reserved.