Query obviously from connector. Works in 11.3.3 MariaDB [test]> 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\G *************************** 1. row *************************** auto_increment_increment: 1 character_set_client: utf8mb3 character_set_connection: utf8mb3 character_set_results: utf8mb3 character_set_server: latin1 collation_server: latin1_swedish_ci collation_connection: utf8mb3_general_ci init_connect: interactive_timeout: 28800 license: GPL lower_case_table_names: 0 max_allowed_packet: 16777216 net_write_timeout: 60 performance_schema: 0 sql_mode: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION system_time_zone: AEDT time_zone: SYSTEM transaction_isolation: REPEATABLE-READ wait_timeout: 28800 1 row in set (0.001 sec) MariaDB [test]> select version(); +----------------+ | version() | +----------------+ | 11.3.3-MariaDB | +----------------+ 1 row in set (0.000 sec) Obviously fails in earlier versions: MariaDB [test]> 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\G ERROR 1193 (HY000): Unknown system variable 'transaction_isolation' MariaDB [test]> select version(); +-----------------+ | version() | +-----------------+ | 10.11.8-MariaDB | +-----------------+ 1 row in set (0.000 sec) Are you sure you have the right version of MariaDB that you described? Otherwise upgrade/use MariaDB Connector/J. On Thu, 21 Mar 2024 at 04:45, <juanhernandez98@gmail.com> wrote:

Just as a FYI, I enabled the MariaDB general logs:

And I'm getting this when the jira instance tries and connect to my mriadb server:

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

-----Original Message----- From: Daniel Black via discuss <discuss@lists.mariadb.org> Sent: Tuesday, March 19, 2024 9:57 PM To: discuss@lists.mariadb.org Subject: [MariaDB discuss] Re: Setting up a jira self hosted instance

On Wed, 20 Mar 2024 at 07:20, Juan Hernandez via discuss <discuss@lists.mariadb.org> wrote:

...

Hi,

So I’ve been running MariaDB 11.3 for a while. I have various applications working great with this server.

I want to setup a Jira 9.14 self hosted instance on one of my servers. I see mariadb.com uses Jira.

So I put the mysql java connector v8.3.0, and the mariadb java connector v3.3.3 installed in my /opt/Atlassian/jira/lib directory.

I tried connecting jira via the setup web interface to my maria db, using the mysql 8.0 driver, and I get the error that I’m not running the right version.

Is that from the driver or from JIRA?

...

I then added under [mysqld] in my.cnf, version = “8.0.25-0” and now get the below error.

...

Error connecting to database

Unknown system variable 'transaction_isolation'

https://jira.mariadb.org/browse/MDEV-21921 - added this to 11.1, so you should be right in 11.3. Its not 10.11.3 right?

Can JIRA use the MariaDB Java Connector v3.3.3?

A last resort is to specify the version=5.7.44 (any 5.7) and/or use a 5.7 compatible mysql java connector.

...

I am now getting this error when testing the connection in jira:

I don’t want to setup a postgresql instance or a mysql 8 instance, can I get this to work? Any help would be greatly appreciated.

Us too. We're still battling against JIRA supported databases a little after all these years. _______________________________________________ discuss mailing list -- discuss@lists.mariadb.org To unsubscribe send an email to discuss-leave@lists.mariadb.org