Comments - MariaDB 10.3.32 and Jira 8.20 - possible? I can't get the set-up right

Hi, i'm running into the exact same problem right now.

I'm trying to run Jira 9.11.3 as a Docker container and MariaDB 11.1.3. on my Windows host system with the newest MariaDB Java Connector 3.3.0 and also the older 2.7.11.

No matter what --version="x.y.z" i'm setting, the error stays the same.

Is there any update on that topic? Any help would be appreciated.

Greetings Dennis

I am trying to configure Jira 9.14 with MariaDB 11.3.2. I set version="8.0.25-0" in my.cnf under [mysqld] but I am getting the below error when testing the connection in the Jira web setup:

Error connecting to database

Unknown system variable 'transaction_isolation'

Any help would be greatly appreciated.

MariaDB has had the transaction_isolation variable since 11.1, so perhaps this a connector issue? Which connector are you using?

I have the jar files in /opt/atlassian/jira/lib for:

mysql-connector-j-8.3.0.jar mariadb-java-client-3.3.3.jar

Do I need any other jar files for the connectors?

Best,

Juan

Also, the Jira setup instance is able to connect to my mariadb server because the general query log is showing this: 240319 14:28:23 239 Connect jira@localhost on jira using TCP/IP 239 Query SET SESSION default_storage_engine=InnoDB 239 Query /* mysql-connector-j-8.3.0 (Revision: 805f872a57875f311cb82487efcfb070411a3fa0) */SELECT @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@collation_server AS collation_server, @@collation_connection AS collation_connection, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout, @@license AS license, @@lower_case_table_names AS lower_case_table_names, @@max_allowed_packet AS max_allowed_packet, @@net_write_timeout AS net_write_timeout, @@performance_schema AS performance_schema, @@sql_mode AS sql_mode, @@system_time_zone AS system_time_zone, @@time_zone AS time_zone, @@transaction_isolation AS transaction_isolation, @@wait_timeout AS wait_timeout

Enable the MariaDB general query log to see what Jira is querying before deciding its not MySQL.

Consider faking to the MySQL-5.7 version in --version and dbconfig.xml.

This blog, a few years old but https://mariadb.com/resources/blog/updating-jira-on-mariadb-and-running-into-database-driver-problems/ (not version 8.0).

You can also fake the server version with https://mariadb.com/kb/en/server-system-variables/#version

Obviously our jira.mariadb.org is on v8.13.13. I'm chasing up the admin to see if there's any other tips.

Thank you for the hint, I tried setting the version with

In PhpMyAdmin I see the version 8.13.13, the database works.

But when I start the Jira Database Configurarion again, I still get the error message "MySQL 8 was selected but underlying database reports a different version." :-(

I think, I need a value for the version that Jira accept...