MariaDB Connector/J 2.2.3 Changelog

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

DownloadRelease NotesChangelogConnector/J Overview

Release date: 9 Mar 2018

For the highlights of this release, see therelease notes.

The revision number links will take you to the revision's page on GitHub. OnGitHub you can view more details of the revision and view diffs of the code modified in that revision.

• Revision #0387d67c - bump 2.2.3 version

• Revision #da0da674 - [misc] checkstyle review correction

• Revision #b3a368d0 - [CONJ-586] test correction

• Revision #6bd14426 - [CONJ-534] Connection.isValid() must be routed to Master and Slave connections to avoid any server timeout

• Revision #aa2bf8b6 - [CONJ-586] erronous transaction state when first command result as error

• Revision #37222ea6 - [CONJ-583] when using option 'allowMasterDownConnection', changing read-only status can expect master connection to be down

• Revision #1f1f6d16 - [CONJ-583] not throwing connection exception if master if down and allowMasterDownConnection is set

• Revision #daaf8a10 - [misc] using maxscale 2.2.2

• Revision #0989045a - [CONJ-583] ensuring that socket exception throw an issue for internal connection query

• Revision #d4b668bc - [CONJ-583] ensuring test reliability

• Revision #86020a2f - [CONJ-583] Additional to ensure connection state when using intermediate proxy. If a failover occurs during this internal queries, and there is some intermediate proxy that doesn't do is the job, even writing to socket doesn't permit to ensure socket

• gitrevj: state, leaving the driver hanging indefinitely. Socket timeout is set for internal connection queries

• Revision #ae52eee6 - [CONJ-583] correcting possible hang when a failover occur during establishment of connection in a master/slave configuration

• Revision #2c260c5e - [misc] change badge labels

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