OH3.1.0.M2: No data will be written to JDBC MariaDB

Hello,
I’ve some trouble with persistence for OH3.1.0.M2. No data are written to the database.
I use already a MariaDB persistence for OH2.5.0 natively on a Synology NAS (wo/ problems).
OH3.1.0.M2 is installed on the same NAS via Docker with the following jdbc.cfg (is a different DB than the one for OH2.5):

url=jdbc:mariadb://localhost:3307/openhabA?serverTimezone=Europe/Berlin
user=openhab
password=xxxxx
waitTimeout=28800

jdbc.persist is

Strategies {
everyMinute : "0 * * * * ?"
default = everyChange
}

Items {
Solar1_Voltage: strategy = everyChange
Solar1_Power: strategy = everyChange
}

Log looks good (for me):

2021-03-06 23:31:06.085 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC::activate: persistence service activated
2021-03-06 23:31:06.086 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC::updateConfig
2021-03-06 23:31:06.097 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::JdbcConfiguration
2021-03-06 23:31:06.117 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: configuration size = 12
2021-03-06 23:31:06.131 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: user=openhab
2021-03-06 23:31:06.132 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: password exists? true
2021-03-06 23:31:06.134 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: url=jdbc:mariadb://localhost:3307/openhabA?serverTimezone=Europe/Berlin
2021-03-06 23:31:06.135 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: found serviceName = 'mariadb'
2021-03-06 23:31:06.136 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: Init Data Access Object Class: 'org.openhab.persistence.jdbc.db.JdbcMariadbDAO'
2021-03-06 23:31:06.142 [DEBUG] [nhab.persistence.jdbc.db.JdbcBaseDAO] - JDBC::initSqlTypes: Initialize the type array
2021-03-06 23:31:06.143 [DEBUG] [nhab.persistence.jdbc.db.JdbcBaseDAO] - JDBC::initSqlQueries: 'JdbcMariadbDAO'
2021-03-06 23:31:06.145 [DEBUG] [b.persistence.jdbc.db.JdbcMariadbDAO] - JDBC::initSqlTypes: Initialize the type array
2021-03-06 23:31:06.152 [DEBUG] [b.persistence.jdbc.db.JdbcMariadbDAO] - JDBC::initSqlQueries: 'JdbcMariadbDAO'
2021-03-06 23:31:06.153 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: dBDAO ClassName=org.openhab.persistence.jdbc.db.JdbcMariadbDAO
2021-03-06 23:31:06.155 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: tableUseRealItemNames=true
2021-03-06 23:31:06.157 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: enableLogTime false
2021-03-06 23:31:06.248 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: load JDBC-driverClass was successful: 'org.mariadb.jdbc.Driver'
2021-03-06 23:31:06.262 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::updateConfig: configuration complete. service=jdbc
2021-03-06 23:31:06.264 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::pingDB
2021-03-06 23:31:06.274 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::openConnection isDriverAvailable: true
2021-03-06 23:31:06.283 [INFO ] [persistence.jdbc.internal.JdbcMapper] - JDBC::openConnection: Driver is available::Yank setupDataSource
2021-03-06 23:31:06.512 [INFO ] [g.discovery.internal.PersistentInbox] - Added new 
2021-03-06 23:31:06.717 [DEBUG] [ence.jdbc.internal.JdbcConfiguration] - JDBC::setDbConnected true
2021-03-06 23:31:06.719 [DEBUG] [b.persistence.jdbc.db.JdbcMariadbDAO] - JDBC::initAfterFirstDbConnection: Initializing step, after db is connected.
2021-03-06 23:31:06.767 [DEBUG] [ab.persistence.jdbc.utils.DbMetaData] - dbMajorVersion = '10'
2021-03-06 23:31:06.769 [DEBUG] [ab.persistence.jdbc.utils.DbMetaData] - dbMinorVersion = '3'
2021-03-06 23:31:06.771 [DEBUG] [ab.persistence.jdbc.utils.DbMetaData] - driverMajorVersion = '1'
2021-03-06 23:31:06.773 [DEBUG] [ab.persistence.jdbc.utils.DbMetaData] - driverMinorVersion = '4'
2021-03-06 23:31:06.778 [DEBUG] [ab.persistence.jdbc.utils.DbMetaData] - dbProductName = 'MySQL'
2021-03-06 23:31:06.781 [DEBUG] [ab.persistence.jdbc.utils.DbMetaData] - dbProductVersion = '10.3.21-MariaDB'
2021-03-06 23:31:06.784 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::pingDB asking db for name as absolutely first db action, after connection is established.
2021-03-06 23:31:06.885 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::checkDBAcessability, first try connection: true
2021-03-06 23:31:06.887 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::createItemsTableIfNot
2021-03-06 23:31:06.898 [DEBUG] [nhab.persistence.jdbc.db.JdbcBaseDAO] - JDBC::doCreateItemsTableIfNot sql=CREATE TABLE IF NOT EXISTS items (ItemId INT NOT NULL AUTO_INCREMENT,itemname VARCHAR(500) NOT NULL,PRIMARY KEY (ItemId))
2021-03-06 23:31:06.911 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::getItemIDTableNames
2021-03-06 23:31:06.913 [DEBUG] [nhab.persistence.jdbc.db.JdbcBaseDAO] - JDBC::doGetItemIDTableNames sql=SELECT itemid, itemname FROM items
2021-03-06 23:31:06.930 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC::getName: returning name 'jdbc' for queryable persistence service.
2021-03-06 23:31:06.936 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC::updateConfig: configuration complete for service=jdbc.
2021-03-06 23:31:06.938 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC::getName: returning name 'jdbc' for queryable persistence service.
2021-03-06 23:31:06.940 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC::getName: returning name 'jdbc' for queryable persistence service.

There are no more JDBC related messages in openhab.log. The database is not created automatically, I had to create it manually. Without the manual creation there were error messages in the log.
Do you have any idea what I might have done wrong here?
Thank you!

One topic I oberved in this context:
Changes in openhab/conf/services/jdbc.cfg are visible in the UI settings - JDBC Persistence Service.


But changes via this UI settings - JDBC Persistence Service don’t change openhab/conf/services/jdbc.cfg.

Is that by intention?

Yes, that’s how it has always worked. Anything in conf is going to take precedence. Changes made through the UI will not be written back to conf.

Thank you @rlkoshak

The problem seems to not specifically to JDBC MariaDB, also rrd4j is not working as expected. A .rrd file, e.g.
-rw-r--r-- 1 1072 9001 755692 Mar 12 16:05 Garage_Temperatur.rrd
is generated in /userdata/persistence/rrd4j once I open in the UI a channel but according to the timestamp it is never updated and in the analyze window no data points are visible. I’ve no rrd4j specific configuration, and have rrd4j as default service for persistence configured.
Not sure if it is related to the MariaDB issue.

edit: Since I couldn’t find the cause of the problem, I started with a fresh installation. With this I have no longer a problem with the persistence.