Download Release Notes Changelog Connector/J Overview

Release date: 1 Jul 2025

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

Notable Changes

• Added caching option for loadCodecs results to improve performance (CONJ-1261)

  • Added new option cachedCodecs

Bugs Fixed

• Fixed incorrect type definitions in DatabaseMetaData.getTypeInfo() (CONJ-1234)

• Resolved potential race condition that could cause NullPointerException (CONJ-1247)

• avoids redundant queries for CallableStatement.getParameterMetaData() (CONJ-1250)

• Fixed SSL configuration issue where zero SSL settings only functioned without explicit SSL configuration (CONJ-1251)

• Resolved GSSAPI authentication error when server exchanges begin with 0x01 byte (CONJ-1252)

• Corrected DatabaseMetadata.getTypeInfo() returning incorrect values for AUTO_INCREMENT, FIXED_PREC_SCALE, and CASE_SENSITIVE fields (CONJ-1254)

• Fixed getString method on BIT(1) fields to properly honor transformedBitIsBoolean configuration (CONJ-1255)

• Enhanced metadata compatibility with MariaDB version 12.0 (CONJ-1259)

• Improved performance of DatabaseMetaData.getExportedKeys method (CONJ-1260)

  • Added new option metaExportedKeys

• Fixed issue to ensure correct catalog name is returned (CONJ-1256)

Changelog

For a complete list of changes made in MariaDB Connector/J 3.5.4, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

Download Release Notes Changelog Connector/J Overview

Release date: 27 Mar 2025

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

Notable Changes

• Resolved timestamp string representation incompatibility between versions 2.7 and 3.x (CONJ-1232) Added new option oldModeNoPrecisionTimestamp

• Modified redirection option to enable by default only when SSL is enabled (CONJ-1235)

Bugs Fixed

Date and Time Handling

• Fixed issue where dates containing zero day or month resulted in a DateTimeException (CONJ-1226)

Result Set and Metadata

• Fixed incorrect values returned by ResultSet.getColumnType() for unsigned values (CONJ-1222)

• Corrected regression in 3.x affecting column metadata for unsigned types (CONJ-1241)

• Fixed CallableStatement.getParameterMetadata() returning wrong java.sql.Type for boolean values (CONJ-1243)

Connection Management

• Prevented NPE (Null Pointer Exception) after reconnection failure in high availability configurations (CONJ-1236)

• Fixed issue with incorrect statements.isClosed value after closing connection (CONJ-1237)

Protocol and Performance

• Disabled BULK operations when no parameters are present (CONJ-1239)

• Fixed connectivity issues with databases that only accept TLSv1.3 (CONJ-1240)

Changelog

For a complete list of changes made in MariaDB Connector/J 3.5.3, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 11 Feb 2025

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable change

• CONJ-1229 Permit executeQuery commands to not return a result-set

Bugs Fixed

• CONJ-1228 The method result-set.getObject(val) for a field of type BLOB returns an object of type Blob by default instead of the expected object of type byte[].

  • The following methods are not affected

    • resultset.getBytes(val)

    • resultset.getBlob(val)

    • resultset.getObject(val, byte[].class)

    • resultset.getObject(val, Blob.class) all returns expected type)

• CONJ-1225 System throws an SQLTimeoutException prematurely without checking all available connections

• CONJ-1221 DatabaseMetadata.getTypeInfo() is missing the data types UUID and VECTOR

• CONJ-1218 Incorrect behavior where XA connections are closed when regular connections are terminated - this is against JDBC specifications

• CONJ-1217 When using the parameter trustCertificateKeyStorePassword, alias for trustStorePassword, an exception is thrown

• CONJ-660 The connection option disconnectOnExpiredPasswords was not handled by the connector..It controls the client behavior when connecting with an expired password.

  • When set to true (default), the client disconnects if it detects an expired password.

  • When false, the client maintains the connection and allows setting a new password.

Changelog

For a complete list of changes made in MariaDB Connector/J 3.5.2, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 20 Nov 2024

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

The MariaDB Connector/J 3.5 release series is replacing the maintenance releases for the 3.4 release series, as the new release series is fully compatible with 3.4.

Notable changes

PARSEC Authentication - CONJ-1193

Support of the PARSEC Authentication Plugin which is provided starting with MariaDB Server 11.6. See parsec documentation for more details.

This requires java 15+ (to use java native ed25519 Algorithm implementation). For previous versions of java, this will require adding BouncyCastle as dependency.

While initially documented in 3.5.0, this feature was not in the released version.

New High Availability Mode With Loadbalancing For Reads - CONJ-1207

When running a multi-master cluster (i.e. MariaDB Cluster with Galera), writing to more than one node can lead to optimistic locking errors ("deadlocks") in some use cases. Writing concurrently to multiple nodes also doesn't result in performance improvements, due to having to synchronously replicate to all nodes. The new high availability mode “Load-balance-read” permits the use of masters in a failover manner (try first master, the next one if the first master fails) while distributing the load on replicas.

Example of connection string:

jdbc:mariadb:load-balance-read://127.0.0.5,127.0.0.6,address=(host=127.0.0.7)(type=replica),address=(host=127.0.0.8)(type=replica)/DB

Equivalent of:

jdbc:mariadb:load-balance-read://address=(host=127.0.0.5)(type=primary),address=(host=127.0.0.6)(type=primary),address=(host=127.0.0.7)(type=replica),address=(host=127.0.0.8)(type=replica)/DB

In the example the hosts 127.0.0.5, 127.0.0.6 will be used for writes, in a failover manner. 127.0.0.6,127.0.0.7 are of type replica, read load balancing will be used.

Permit bulk for INSERT ON DUPLICATE KEY UPDATE commands for 11.5.1+ servers - CONJ-1208

Since MDEV-30366, the server can return appropriate detailed answers. This was implemented, but not for specific INSERT ON DUPLICATE KEY UPDATE commands.

Bugs Fixed

• CONJ-1053 waffle-jna dependency is not declared optional in the module description

• CONJ-1196 setObject on java.util.Date is en/decode as java.sql.Date and truncates hour/minutes/seconds/ms while it must be en/decode like a java.sql.Timestamp

• CONJ-1211 JDBC 4.3 enquoteIdentifier missing validation

  • An identifier containing only number must be quoted, even if alwaysQuote parameter is set to false

  • Length validation must be done (< 64 characters).

• CONJ-1213 SQL commands ending with semicolon and trailing space are not using bulk

Changelog

For a complete list of changes made in MariaDB Connector/J 3.5.1, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 24 Oct 2024

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

The MariaDB Connector/J 3.5 release series is replacing the maintenance releases for the 3.4 release series, as the new release series is fully compatible with 3.4.

Notable changes

PARSEC Authentication - CONJ-1193

Support of the PARSEC Authentication Plugin which is provided starting with MariaDB Server 11.6. See parsec documentation for more details.

This requires java 15+ (to use java native ed25519 Algorithm implementation). For previous versions of java, this will require adding BouncyCastle as dependency.

New options truststore, trustStorePassword and trustStoreType - CONJ-1183

Those options permit the use of a specific truststore that differs from the Java default truststore. This has been added for MariaDB 2.x and MySQL connector compatibility. See documentation

New option connectionCollation - CONJ-1199

The Connector is using the utf8mb4 charset per default when establishing a connection. ‘connectionCollation’ can be used to define which utf8mb4 collation should be used. If not set the server default collation for utf8mb4 will be used.

Starting with MariaDB 11.4 we recommend to instead set character_set_collations

Support for methods setObject/getObject and setArray/getArray - CONJ-1205

This addition is a preparation for the Vector support of MariaDB Server

Example of Array:

Array valArray = connection.createArrayOf("float", new float[] {1, 2, 3}); 
try (PreparedStatement prep = 
connection.prepareStatement("INSERT INTO BinaryCodec(t0, t1) VALUES (?, ?, ?)")) { 
prep.setInt(1, 1); 
prep.setArray(2, valArray); 
prep.setObject(3, new float[] {4, 5, 6}); 
prep.execute(); 
}

Resultset:

Array resArray = rs.getArray(2); 
float[] res = rs.getObject(2, float[].class);

Bugs Fixed

• CONJ-1202 A change of the collation via a session variable might be ignored

• CONJ-1201 Incorrect default behavior for forceConnectionTimeZoneToSession

  • NOTE: If client and server use different time zones and no timezone options where used, MariaDB Connector/J 3.4 introduces a change which is forcing client timezone to the session. This behavior is an not intended incompatibility change compared to MariaDB Connector/J 3.3, which is corrected in MariaDB Connector/J 3.5 with this change

• CONJ-1200 Batch import fails with exception "Unknown command"

• CONJ-1187 Throw exception type SQLTimeoutException instead of SQLNonTransientConnectionException for connection timeouts

Changelog

For a complete list of changes made in MariaDB Connector/J 3.5.0, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 27 Mar 2025

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-1237: Fixed issue with incorrect statements.isClosed value after closing connection

• CONJ-1236: Prevented NPE (Null Pointer Exception) after reconnection failure in high availability configurations

• CONJ-1239: Disabled BULK operations when no parameters are present

Changelog

For a complete list of changes made in MariaDB Connector/J 3.4.2, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 17 Jul 2024

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

Implementation of pinGlobalTxToPhysicalConnection for XA Connection

For CONJ-1189

The new boolean option pinGlobalTxToPhysicalConnection, when enabled, ensures that an operation for a specific XID is routed to the same connection, to permit supporting XA START <xid> when XA END has been called. This prevent errors like

XA resource 'xaDataSource': resume for XID 'XID: <some id>' raised -5: invalid arguments were given for the XA operation

Enhanced host description

For CONJ-685/CONJ-686

The host description for connecting to the server has been changed from either <host>[:<portnumber>] or address=(host=<host>)[(port=<portnumber>)][(type=(master|slave))] to a more detaild host description, permitting to set localsocket or pipe, and to define a specific ssl mode depending on the host. New format:

address=(host=<host>|localSocket=<socket>|pipe=<namedpipe>)[(port=<portnumber>)][(type=(master|slave))][(sslMode=disable|trust|verify-ca|verify-full)]

Example:

jdbc:mariadb:sequential://address=(localSocket=/socket),address=(host=10.0.0.1)(port=3306)(sslMode=verify-full)/DB

This connection string now permits to use a local unix socket if available, and host 10.0.0.1 with ssl if the unix socket is not available. A detailed host description option supersedes a global option description. The previous example can also be written in the following way, defining different ssl modes for both host options:

jdbc:mariadb:sequential://address=(localSocket=/socket)(sslMode=disable),10.0.0.1:3306/DB?sslMode=verify-full

Adding databaseTerm alias

For CONJ-1190

Option useCatalogTerm has an alias databaseTerm for MySQL connector compatibility.

Bugs Fixed

• CONJ-1181 The validation of a statement of the cache for prepared statements is not taking the use of different schemas into account, which can result in unexpected behavior when the same statement is executed on different schemas.

• CONJ-1178 DatabaseMetaData.getImportedKeys returns a different PK_NAME value than DatabaseMetaData.getExportedKeys when using a NON UNIQUE constraint.

• CONJ-1180 Slow performance of function DatabaseMeta.getExportedKeys()

• CONJ-1185 Android app incompatibility, regex CANON_EQ flag is not supported on Android OS

• CONJ-1188 Database meta getSQLKeywords is listing all reserved keywords, not only the restricted keywords

• CONJ-1191 The Function metadata getImportedKeys is slow when a database has not been set

• CONJ-1068 The Function ResultSetMetaData.getColumnTypeName() returns type VARCHAR instead of type TINYTEXT for columns of type TINYTEXT

• CONJ-1182 Missing error mapping for errors XA_RBTIMEOUT, XA_RBTIMEOUT and XA_RBDEADLOCK

Changelog

For a complete list of changes made in MariaDB Connector/J 3.4.1, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 17 May 2024

MariaDB Connector/J 3.4.0 is a Stable (GA) release, and replaces 3.3 as the maintenance releases.

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

CONJ-1105 ZERO-CONFIGURATION SSL ENCRYPTION

Using SSL (a more correct term would be TLS, but in reality SSL is more commonly used) has been simplified with MariaDB Server 11.4. Before version 11.4, proper SSL configuration required multiple manual steps for the server and all the clients connecting to it.

For MariaDB Connector/J before 3.4 to establish an SSL encrypted connection, or a MariaDB Server release series previous to 11.4, three options can be used:

• Have server certificates generated with trusted Certificate Authorities (CA), using a configuration like: sslMode=verify-full

• Configure the connector using a server certificate, like: sslMode=verify-full&serverSslCert=file:///server-cert.pem

• Disable the verification of the SSL certificate, which is insecure and not recommended, using a configuration like: sslMode=trust

For MariaDB Connector/J 3.4 to establish an SSL encrypted connection to MariaDB Server 11.4, enabling SSL does not require any special configuration apart from using sslMode=verify-full. The connector doesn't need to know the server certificate anymore, as long as the password is not empty.

CONJ-1171 Changes to Timezone Configuration Options for TIMESTAMPS

The MariaDB Connector/J versions before 3.4 provide a single "timezone" option for working with different time zones for clients and servers. While this functionality remains compatible, it's now separated into two distinct settings:

• connectionTimeZone

• forceConnectionTimeZoneToSession

There are now 3 options that control timestamps behavior in the java connector:

• connectionTimeZone: (LOCAL | SERVER | ) This option defines the connection's time zone. LOCAL retrieves the JVM's default time zone, SERVER fetches the server's global time zone upon connection creation, and allows specifying a server time zone without requesting it during connection establishment.

• forceConnectionTimeZoneToSession: (true | false) This setting dictates whether the connector enforces the connection time zone for the session.

• preserveInstants: (true | false) This option controls whether the connector converts Timestamp values to the connection's time zone.

While remaining compatible with previous versions, this permits more flexibility when handling timezone difference scenarios. See timezone documentation for detailed information.

CONJ-981 Add support for connection redirection

Since MariaDB 10.3.1, the server has a new system variable redirect_url to provide a connection string using the forma mariadb/mysql://[<user>[:<password>]@]<host>[:<port>]/[<db>[?<opt1>=<value1>[&<opt2>=<value2>]]].

When set, all existing connections will be redirected to the designated URL values when appropriate. A connection will only be redirected when no transaction is active.

Example for enabling the redirection:set @@global.redirect_url="mariadb://somehost:3306/"

The redirection feature is enabled by default. It can be disabled by setting the new option permitRedirect to FALSE, which will result in ignoring the redirection URL.

CONJ-1154 Reduced overhead for issuing queries for retrieving and setting isolation level metadata

When session tracking is supported by the MariaDB Server release series, Connection.getTransactionIsolation() won’t query the server as the current state is already known from the session tracking information. Connection.setTransactionIsolation will skip the query to set the transaction isolation level if the server is already using the requested transaction isolation level.

Bugs Fixed

• CONJ-1103 Connector/J Version 3 Does Not Respect "nullCatalogMeansCurrent" Property

• CONJ-1161 Database connection failing on android

• CONJ-1107 MariaDB Connector 3 no longer supports query timeout with MySQL

• CONJ-1125 Inconsistency in Handling PreparedStatement.executeQuery() between MariaDB and MySQL Connectors

• CONJ-1156 getTables should be ordered as expected

• CONJ-1163 jdbcCompliantTruncation Does Not Appear To Be Working

• CONJ-1164 Variable initialization ahead of LOAD DATA INFILE not possible by validateLocalFileName pattern

• CONJ-1168 useBulkStmts compatibility value with pre 3.2 version

• CONJ-1169 improve Client prepared statement setMaxRows implementation

• CONJ-1170 OFFSET missing from getSQLKeywords

• CONJ-1158 DatabaseMetaData#getFunctions's result not property ordered

• CONJ-1159 DatabaseMetaData#getClientInfoProperties not ordered correctly

• CONJ-1166 Implement connection properties fallbackToSystemKeyStore and fallbackToSystemTrustStore

• CONJ-1173 Bulk implementation returning individual results

• CONJ-1174 ConnectorJ gives precision of 20 for signed bigint

• CONJ-1100 Be able to filter system tables and views

Changelog

For a complete list of changes made in MariaDB Connector/J 3.4.0, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 27 Mar 2025

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-1237: Fixed issue with incorrect statements.isClosed value after closing connection

• CONJ-1236: Prevented NPE (Null Pointer Exception) after reconnection failure in high availability configurations

• CONJ-1239: Disabled BULK operations when no parameters are present

Changelog

For a complete list of changes made in MariaDB Connector/J 3.3.4, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 20 Feb 2024

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-1050 regression: nonparameterized batch fails

• CONJ-1150 Error using PrepareStatement.setURL with null url

• CONJ-1152 Improve message when reaching socket timeout during connection initial commands

Changelog

For a complete list of changes made in MariaDB Connector/J 3.3.3, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 19 Dec 2023

MariaDB Connector/J 3.3.2 is a Stable (GA) release, and will replace 3.2 as the maintenance releases.

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-1117 new option returnMultiValuesGeneratedIds for connector 2.x compatibility, so getGeneratedKeys() return all ids of multi-value inserts

• CONJ-1140 regression caussing ClassCastException on DatabaseMetaData when use with option defaultFetchSize set

• CONJ-1129 Metadata.getPrimaryKeys table comparison using like in place of strict equality

• CONJ-1130 ensuring batch parameter are cleared after SQL Failure

• CONJ-1131 NullPointerException when Calling getGeneratedKeys() after an SQL Failure

• CONJ-1132 Ensuring reseting result for getUpdateCount() after an SQL Failure

• CONJ-1135 ensuring BULK command not used when using INSERT ON DUPLICATE KEY UPDATE in order to always have unique affected rows by default

• CONJ-1136 wrong decoding for Resultset.getByte() results for binary varchar fields

• CONJ-1137 ensuring never having NPE in OkPacket when setting auto commit

• CONJ-1138 Inconsistency in Behavior of PreparedStatement After closeOnCompletion() Between MariaDB and MySQL Connectors

• CONJ-1049 Metadata getTableTypes result was not ordered by TABLE_TYPE

Changelog

For a complete list of changes made in MariaDB Connector/J 3.3.2, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 29 Nov 2023

MariaDB Connector/J 3.3.1 is a Stable (GA) release, and will replace 3.2 as the maintenance releases.

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-1120 java 8 compatibility error in 3.3.0

• CONJ-1123 missing OSGi javax.crypto dependency

• CONJ-1124 ensure not having OOM when setting huge fetch size

• CONJ-1109 Regression in clearBatch() for parameterized statements

• CONJ-1126 setting fetchSize directly on a ResultSet object does not reflect the expected change

• CONJ-1127 Statement.getResultSetType () failed to change the result set type

• CONJ-1128 Setting Negative Fetch Size on ResultSet Without Throwing Error

Changelog

For a complete list of changes made in MariaDB Connector/J 3.3.1, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 08 Nov 2023

MariaDB Connector/J 3.3.0 is a Stable (GA) release, and will replace 3.2 as the maintenance releases.

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

• CONJ-1115 Make connector become more virtual-thread friendly

• CONJ-1108 Database metadata listing TEMPORARY tables/sequences

• CONJ-1113 update ed25519 to recent version

• CONJ-1116 Avoid unnecessary synchronization on calendar when no calendar parameter

Bugs Fixed

• CONJ-1102 BatchUpdateException.getUpdateCounts() returns SUCCESS_NO_INFO but expects EXECUTE_FAILED

Changelog

For a complete list of changes made in MariaDB Connector/J 3.3.0, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 25 Aug 2023

MariaDB Connector/J 3.2.0 is a Stable (GA) release. It is replacing 3.1 as the maintenance releases.

This is the last release of the 3.2 release series as the release series 3.3 is compatible and is therefore replacing 3.2 as the maintenance releases.

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

Batch Bulk behavior

CONJ-920

Bulk batching enabled by default (option useBulkStmts) with permit super fast batching, but batch return array of update counts with Statement.SUCCESS_NO_INFO values. The problem is that application using optimistic locking fails, expecting exact return value.

useBulkStmts is now defaulting to false, with the addition of a new option useBulkStmtsForInserts, enabled by default permit to enable bulk for insert command only. This permit to have return values in batching return value, for all cases, permitting optimistic behavior.

This default values are more appropriate for all kind of application. If application doesn't use optimistic locking, enabling useBulkStmts is then more appropriate, because UPDATE and DELETE commands in batch will then use faster BULK implementation.

Maxscale improvement

CONJ-1084

When using maxscale 23.08.0+, when a maxscale node fails, connector will now priorize reconnection to the maxscales nodes having less connections, to ensure connections repartition after failover. This allows a faster return to normal

other features

• CONJ-1088 Implement databaseTerm option for mysql compatibility

• CONJ-1096 adding option useLocalSessionState to permit avoiding queries when application only use JDBC methods.

Bugs Fixed

• CONJ-1075 LOAD DATA INFILE is broken on windows

• CONJ-1079 getGeneratedKeys after batch will not return all generated id's if first batch command return no generated id.

• CONJ-1080 maridb Java connector sslMode=verify-ca complaining unable to find trust certificate.

• CONJ-1082 Multiple session system variables parsing fails

• CONJ-1083 Using /client prepare/ prefix to force client side prepared statement

• CONJ-1091 can't make a connection when the Read Replica DB is in a hang state when SocketTimeout=0 set

• CONJ-1092 ensure respecting server collation

• CONJ-1094 Missing mariadb/mysql collation

Changelog

For a complete list of changes made in MariaDB Connector/J 3.2.0, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 1 May 2023

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

This is the last release of the 3.1 release series as the release series 3.2 is compatible and is therefore replacing 3.1 as the maintenance releases.

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bug fixed

• CONJ-1065 wrong Resultset.wasNull() for zero-date timestamps

• CONJ-1070 getBlob on TEXT columns throw Exception

• CONJ-1071 Error response during Bulk execution might result in connection wrong state

• CONJ-1067 When some numeric data types are set to UNSIGNED, ResultSetMetaData.getColumnTypeName() does not return UNSIGNED

Changelog

For a complete list of changes made in MariaDB Connector/J 3.1.4, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 22 Mar 2023

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bug fixed

• CONJ-1054 Threadsafety issue when using CredentialPlugin in v3.x

• CONJ-1056 JDBC connector reads incorrect data from unix socket when reading packet size > 32K

• CONJ-1057 Wrong decoding of binary time with value "00:00:00"

• CONJ-1058 JDBC 4.3 org.mariadb.jdbc.Statement enquote* methods implementation. thanks to @peterhalicky

• CONJ-1060 BIT default metadata doesn't take care of transformedBitIsBoolean option

• report 2.7.9 bug fixes :

  • CONJ-1062 correcting TlsSocketPlugin to use Driver classloader

  • CONJ-1063 DatabaseMetaData.getTypeInfo() returns wrong value for UNSIGNED_ATTRIBUTE

Changelog

For a complete list of changes made in MariaDB Connector/J 3.1.3, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 24 Jan 2023

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

• CONJ-1042 fix DatabaseMetaData.getColumns() on old server version (< MySQL 5.6.4 and < MariaDB 5.3.0)

Bug fixed

• CONJ-1040 possible ConcurrentModificationException when parsing properties when connecting

• CONJ-1041 possible ArrayIndexOutOfBoundsException when writing a parameter to socket pre-buffer when pre-buffer is exactly 16M

Changelog

For a complete list of changes made in MariaDB Connector/J 3.1.2, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 11 Jan 2023

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bug fixed

• 3.0.10 bug fix:

  • CONJ-1023 Connector/J doesn't set SSL cap bit in Handshake Response Packet

  • CONJ-1026 timezone=auto option failure on non-fixed-offset zone machine

  • CONJ-1032 Compatibility for deprecated arguments is case sensitive now

• CONJ-1036 org.mariadb.jdbc.client.socket.impl.PacketWriter.writeAscii() broken in 3.1.0

Changelog

For a complete list of changes made in MariaDB Connector/J 3.1.1, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 15 Nov 2022

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Performance

Other than features, connector permit significant performance improvements, reaching the same level of performance than c connector

Most significant change are :

• CONJ-1009 improve performance reading big result-set

• CONJ-1014 avoid creating array when receiving server packet

• CONJ-1015 pipelining sent (PREPARE+EXECUTE) are now sent into a single buffer, permitting in some case to have only one TCP-IP packet for 2 mysql packet.

Benchmark using JMH one a single 4 core ubuntu 22.04 server (AWS c5.xlarge) shows :

simple resultset command : "Select 1"

@Benchmark
  public int run(MyState state) throws Throwable {
    try (Statement st = state.connectionText.createStatement()) {
      ResultSet rs = st.executeQuery("select 1");
      rs.next();
      return rs.getInt(1);
    }
  }

Client side prepared statement parsing : "DO 1000 parameters"

private static final String sql;

  static {
    StringBuilder sb = new StringBuilder("do ?");
    for (int i = 1; i < 1000; i++) {
      sb.append(",?");
    }
    sql = sb.toString();
  }

  @Benchmark
  public int text(MyState state) throws Throwable {
    try (PreparedStatement st = state.connectionText.prepareStatement(sql)) {
      for (int i = 1; i <= 1000; i++) {
        st.setInt(i, i);
      }
      return st.executeUpdate();
    }
  }

resultset with lots of columns : ""select 1 row from a 100 int columns"

@Benchmark
  public int[] text(MyState state) throws Throwable {
    try (PreparedStatement prep = state.connectionText.prepareStatement("select * FROM test100")) {
      ResultSet rs = prep.executeQuery();
      rs.next();
      int[] objs = new int[100];
      for (int i = 0; i < 100; i++) {
        objs[i] = rs.getInt(i + 1);
      }
      return objs;
    }
  }

UUID Object support

Since MariaDB server 10.7, a new UUID data format is supported. getter and setter can now pass java.util.UUID parameter (i.e. PrepareStatement setObject(index, ) / Resultset getObject(index, UUID.class) )

Resultset.getObject without class or type precision will now return UUID object for UUID fields by default

UUID metadata

Metadata for UUID fields will now return ResultSetMetaData.getColumnTypeName(index) => "uuid" ResultSetMetaData.getColumnClassName(index) => "java.util.UUID" ResultSetMetaData.getColumnType(index) => Types.OTHER

replacing :

ResultSetMetaData.getColumnTypeName(index) => "CHAR" ResultSetMetaData.getColumnClassName(index) => "java.lang.String" ResultSetMetaData.getColumnType(index) => Types.CHAR

For compatibility, a new option uuidAsString permit to consider UUID as String like previously.

Other changes

• CONJ-992 load balance hosts are now chosen using ROUND ROBIN in place of RANDOM

• CONJ-1008 default value for socket option useReadAheadInput change to false.

Changelog

For a complete list of changes made in MariaDB Connector/J 3.1.0, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 25 Aug 2023

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

This is the last release of the 3.0 release series as the release series 3.1 is compatible and is therefore replacing 3.0 as the maintenance releases.

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-1089 correcting 3.0.10 incompatibility with java 8

Changelog

For a complete list of changes made in MariaDB Connector/J 3.0.11, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 11 Jan 2023

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-1023 Connector/J doesn't set SSL cap bit in Handshake Response Packet

• CONJ-1026 timezone=auto option failure on non-fixed-offset zone machine

• CONJ-1032 Compatibility for deprecated arguments is case sensitive now

Changelog

For a complete list of changes made in MariaDB Connector/J 3.0.10, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 08 Nov 2022

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

• merge from 2.7.7 : CONJ-1016 avoid splitting BULK command into multiple commands in case of prepareStatement.setNull() use

Bugs Fixed

• merge from 2.7.7 : CONJ-1021 GSSAPI authentication might result in connection reset

• merge from 2.7.7 : CONJ-1019 DatabaseMetaData.getImportedKeys should return real value for PK_NAME column

• CONJ-1012 stored procedure register output parameter as null if set before registerOutParameter command

• CONJ-1017 Calendar possible race condition, cause wrong timestamp setting

Changelog

For a complete list of changes made in MariaDB Connector/J 3.0.9, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 20 Sep 2022

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

• CONJ-1010 improve client side prepared parameter substitution

Bugs Fixed

• CONJ-997 regression in 3.x when using option galeraAllowedState resulting in an IndexOutOfBoundsException

• CONJ-1002 2nd failover reconnection ignores default database/schema setting when not set by connection string

• CONJ-1003 replication configuration always use 1st replica on 3.0

• CONJ-996 BatchUpdateException doesn't inherited the SQLState & vendorCode from the cause SQL exception

• CONJ-1006 disabling cachePrepStmts with useServerPrepStmts might result in Exception

• CONJ-1007 Socket file descriptors are leaked after connecting with unix socket if DB is not up running

• CONJ-999 setting createDatabaseIfNotExist option use on read-only server will refuse connection on 3.0

Changelog

For a complete list of changes made in MariaDB Connector/J 3.0.8, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 4 Aug 2022

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-993 SQLDataException reading DATA_TYPE on DatabaseMetaData.getTypeInfo() after 3.0.4

• CONJ-986 Permit specific Statement.setLocalInfileInputStream for compatibility

• CONJ-987 Version 3.0.0 returns String for VARBINARY instead of byte[] as 2.7.6 did

• CONJ-989 Binary column read as String

• CONJ-990 Setting timezone=UTC result in SQLSyntaxErrorException

• CONJ-991 Regression: binary(16) is returned as String by getObject()

• CONJ-994 Version 3.x rejects previously accepted boolean string parameter for BOOLEAN field

Changelog

For a complete list of changes made in MariaDB Connector/J 3.0.7, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 29 Jun 2022

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

• CONJ-984 Permit executing initial command with new option initSql

• CONJ-976 Improve use of pipelining when allowLocalInfile is enabled

Bugs Fixed

• CONJ-985 ResultSet.getObject() returns ByteSet instead of Byte[] for BIT

• CONJ-953 PreparedStatement.getGeneratedKeys() returns rows when no keys are generated in insert

• CONJ-975 ArrayIndexOutOfBoundsException when attempt to getTime() from ResultSet

• CONJ-979 ResultSet.getObject() returns Byte instead of Boolean for tinyint(1)

• CONJ-980 Permit setObject with java.util.Date parameter

Changelog

For a complete list of changes made in MariaDB Connector/J 3.0.6, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 25 May 2022

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Notable Changes

• CONJ-958 When multiple hosts are defined in the connection URL and no failover or load balancing mode is used, MariaDB Connector/J will try the hosts sequentially until a connection is successful.

• CONJ-961 LOAD DATA LOCAL INFILE is now enabled by default on the client side, for compatibility with MariaDB Connector/J 2.7.

  • The connector validates that only the filename used in the original request will be provided, to prevent a man-in-the-middle change of the filename.

  • This might cause Batch performance regression. In case of non use of LOCAL DATA LOCAL INFILE, disable option allowLocalInfile explicitly can improve performance.

Bugs Fixed

• CONJ-956 ArrayIndexOutOfBoundsException when alias length > 250

• CONJ-947 value after milliseconds precision lost when timestamp is encoded

• CONJ-949 keep clientCertificateKeyStoreUrl and clientCertificateKeyStoreUrl aliases

• CONJ-950 metadata TEXT/TINYTEXT/MEDIUMTEXT/LONGTEXT wrong column type and length

• CONJ-954 java.time.OffsetDateTime not supported

• CONJ-958 compatibility with 2.7: now loop through hosts when multiple host without failover mode

• CONJ-959 java.time.Instant not supported

• CONJ-962 resultset for negative TIME value return erronous LocalDateTime values

• CONJ-965 better error message when not loading serverSslCert file

• CONJ-967 clearParameters() breaks validity when using output parameters in stored procedures

• CONJ-969 org.mariadb.jdbc.ClientPreparedStatement is missing a toString implementation, useful for logging

Changelog

For a complete list of changes made in MariaDB Connector/J 3.0.5, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 25 Mar 2022

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

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

Bugs Fixed

• CONJ-921 DatabaseMetadata#getTables throws a syntax error if a NULL value is used for tableNamePattern

• CONJ-922 A DECIMAL overflow for long/int/short is not throwing an exception

• CONJ-924 A NULL value returned for a column can result in java.lang.IllegalArgumentException: Unexpected data type NULL

• CONJ-926 The authentication is restricted to the methods 'mysql_native_password,client_ed25519,auth_gssapi_client' instead of allowing all supported methods, if the option restrictedAuth is not set (default NULL).

• CONJ-923 32 bit value returned instead of a 64 bit value for generated id / updated rows

• CONJ-933 When the load-balancing HA mode is used a host is not used anymore after a connection failed, even if a connection would be possible again.

• CONJ-935 Connection.getMetaData() returns values of type MariaDbClob instead of the expected type String

• CONJ-937 metadata.getColumnTypeName() returns the values with a wrong types

• CONJ-934 A connection fails if the password is set before the username for MariaDbDataSource

• CONJ-932 The login packet has non-standard length information for the attributes, which can result in issues when using wireshark.

• CONJ-945 When using failover the definition of retriesAllDown is ignored when trying to reconnect

• CONJ-940 Updates of rows is not possible for storage engines which do not provide the metadata information for primary columns

Install and Upgrade

• CONJ-925 missing OSGI metadata is missing

Changelog

For a complete list of changes made in MariaDB Connector/J 3.0.4, with links to detailed information on each push, see the changelog.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

DownloadRelease NotesChangelogConnector/J Overview

Release date: 25 Jan 2022

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

NOTE: MariaDB Connector/J 3.0.3 is NOT fully compatible with the latest release of version 2.7.

For an overview of MariaDB Connector/J see theAbout MariaDB Connector/J page

New version 3.0 is a complete rewrite of the connector, with code simplification, reduced size (15%), more than 90% coverage tested, with performance gain.

Licence is still LGPL-2.1 or later with copyright to MariaDB Corporation AB only (2.x was a fork from Drizzle-JDBC - BSD licensed)

What’s new :

• Binary prepare statement improvement

• faster connection creation

• Support of new 10.6 metadata skip

• Pipelining PREPARE

• REDO failover transaction

• Better java version support

• New option tcpKeepIdle, tcpKeepCount, tcpKeepInterval for java 11+

• Provide a full JPMS module descriptor

• new option restrictedAuth to permit authentication plugin restriction

• metadata queries performance improvement

• Easy logging

• Deprecated option removal

• Support codec registry implementation

Performance

Other than features, connector permit significant performance improvements : Here are real world TPCC benchmarks results, comparing connector version 2.7.4 and 3.0.3

Binary prepare statement improvement

When using option useServerPrepStmts, the connector uses BINARY protocol, meaning executing PREPARE + EXECUTE commands.

Pipelining

Queries issued from the application are sent one by one to the server, waiting on the results of the first query before sending the next. Communication with the server follows this synchronous request-response messaging pattern.

When using binary protocol, a PREPARE command is issued (if not in cache) before executing an EXECUTE command.

For MariaDB server 10.2+, the connector will send an optimistic PREPARE + EXECUTE, sending queries one after another. EXECUTE command will be executed only if the PREPARE command succeeds. This avoids some network latency reading PREPARE result before sending EXECUTE command.

Support of new 10.6 metadata skip

10.6 Server with MDEV-19237 permit to avoid resending metadata when they haven’t changed. This concerns SQL commands that return a resultset, when using option useServerPrepStmts.

Now, the server will send metadata only if they have changed (DDL change for example). This avoids useless information transiting on the network and parsing those metadata.

Connector internal JMH Benchmark results, selecting one row of a 100 int column table :

Avoiding additional command on connection creation

Connection creation by default won't execute additional command to set session environement. Depending on options, there might be a few commands, but driver avoid them to the maximum.

REDO failover transaction

After a failover occurs, reconnection will be automatically done according to high-availability configuration. Even if implementation is now smaller and clearer, the result will be the same.

After reconnection, the connector might still throw an exception if the state is unsure. Failover on replica are transparent. This is different when the failover occurs during the execution of a query on a master server.

A new option transactionReplay permit to replay transactions : Most of the time, queries occur in transactions so redo transaction implementation will solve most of the failover cases transparently. Option is disabled by default. When enabled, all queries in a transaction are cached until transaction resolution. If a failover occurs, the driver will recreate a new connection and replay cache. There is a few limitations: When the last command was a "commit" sent to the server, an exception will be thrown, the driver cannot know the current state. application must have idempotent queries only (queries can be "replayable") If the transaction is too big (cache size limit set with new option transactionReplaySize), the driver won’t cache the transaction anymore, so a failover during that specific transaction will result in throwing an exception.

Better java version support

Driver uses Multi-Release JARs (MRJAR), to simultaneously contain implementations for different versions of java. This permit still supports Java 8, but provides solutions for higher versions of java.

Connector now provides a java 9 full module-info JPMS descriptor

Java 11 socket extended option TCP_KEEPIDLE, TCP_KEEPCOUNT and TCP_KEEPINTERVAL are now configurable with tcpKeepIdle, tcpKeepCount, tcpKeepInterval options respectively. (These options don't have any effect if using a java version lower than 11).

Authentication plugin restriction

A new option restrictedAuth permits to restrict authentication plugins. Example connection string jdbc:mariadb:*localhost/db?restrictedAuth=mysql_native_password,client_ed25519 will restrict plugin use of standard mysql_native_password and client_ed25519 only.*

Metadata queries performance improvement

Metadata queries use of information_schema improvement for partial or exact matching, permitting faster results.

Easy logging

Logging can now be easily enabled at runtime, using slf4j if present, or fallback to JDK logger / console if not.

• INFO level log connection error

• DEBUG/FINE level log commands

• TRACE/FINEST level log network exchanges

jdbc:mariadb scheme

It occurs that mysql AND mariadb driver are sometimes available in the same classpath, so, now, driver only accept jdbc:mariadb: by default.

If for some reason, connection string is required to be jdbc:mysql: Driver will be used only if connection string contain 'permitMysqlScheme'. example :jdbc:mysql:*localhost/test?permitMysqlScheme.*

Option changed

Ssl configuration use now a new option sslMode to simplify configuration Possible value are :

This can still be done by 2.x options (useSsl, disableSslHostnameVerification, trustServerCertificate) for compatibility, but this is the preferred way.

A new option timezone permits to force session timezone in case of client having a different timezone compare to server. if set timezone must to either offset or IANA tz (like '+5:00' or 'America/New_York')': connector will set connection timezone. This replace options useLegacyDatetimeCode and serverTimezone that did cause some problems when using some functions that are affected by the time zone setting.

Option removal

Even if connectors aim to be compatible with the 2.x version, there has been very few option removal since connection exists. This is now the time :