Sever version:10.6.14-MariaDB
my.conf:
[mariadb]
datadir=/app/mariadb/data
log_error=out.err
server_id=1
character_set_server=utf8mb4
collation_server=utf8mb4_bin
init_connect='SET NAMES utf8mb4'
explicit_defaults_for_timestamp=1
lower_case_table_names=1
default-time-zone='+8:00'
transaction_isolation=READ-COMMITTED
tmp_table_size=64M
interactive_timeout=1800
wait_timeout=1800
max_connections=200
max_allowed_packet=32M
read_rnd_buffer_size=8M
sort_buffer_size=8M
join_buffer_size=8M
innodb_force_primary_key=1
innodb_log_buffer_size=16M
innodb_flush_log_at_trx_commit=1
innodb_sort_buffer_size=64M
innodb_log_file_size=512M
innodb_print_all_deadlocks=1
innodb_buffer_pool_size=2G

[client]
default-character-set=utf8mb4

hmm, i've tryed to reproduce the problem without success.
using same config file, mariadb server 10.6.14 and connector 3.1.4 as well.
Driver rely on server information for this, so could you share some other informations on what type of server you are using ?

maybe if connected to a database the current DB engine you are using too would help

The operation system is CentOS 7.9

Database init script:
CREATE SCHEMA test1 DEFAULT CHARACTER SET utf8mb4 collate utf8mb4_bin;
grant all privileges on test1 .* to newsoft@'%' identified by '***';
flush privileges;

The current DB engine: Innodb

AutoCommit method works fine in 2.7.9 strangely.

When remove 'autocommit=0' in my.cnf, AutoCommit method works fine.

ho, i think i remember having seen something like that server returning wrong autocommit state when setting 'autocommit=0' in server conf file, but i've never been able to reproduced it. I'll check.

btw, as a workaround, could you try explicitly set autocommit option on connection string using 'jdbc:mariadb://host/db?autocommit=true'

when appending '?autocommit=true' in jdbcUrl, 'getAutoCommit' method work return correctly

closing since server correction MDEV-32875 now correct behavior