5.2.0final restore of backup is always rollbacked
Hi,
I'm trying to restore a backup that come from a file storage to a new repository that point to a mysql database. (the backup file size is 35Mb)
The restoration process goes well but at the end all modification are rollbacked saying that there is a "dirty commit".
(Hikari autocommit=true)
Do you know the reason of this behaviour? What does "dirty commit" means?
Thank you in advance
Logs:
19:28:05.202 [wisdom-system-executor-10] DEBUG com.zaxxer.hikari.pool.PoolBase - HikariPool-0 - Reset (autoCommit, isolation) on connection com.mysql.jdbc.JDBC4Connection@71673bd1
19:28:05.307 [wisdom-system-executor-10] DEBUG org.modeshape.jcr.BackupService - restoring documents batch [180000, 180779]
19:28:05.307 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - New transaction '4a848140-8dfb-4bf7-9c59-49e03dc6affe' started by ModeShape...
19:28:05.310 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - New DB connection allocated for tx '4a848140-8dfb-4bf7-9c59-49e03dc6affe'
19:28:05.316 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - Received committed notification for transaction '4a848140-8dfb-4bf7-9c59-49e03dc6affe'
19:28:05.334 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - Committing the active connection for transaction 4a848140-8dfb-4bf7-9c59-49e03dc6affe with the changes: {a7ca237317f1e7jcr:system/mode:metadata={ "metadata" : { [...LOT OF JSON HERE...]
19:28:05.378 [wisdom-system-executor-10] DEBUG o.m.p.relational.DefaultStatements - adding batch statement: INSERT INTO MODESHAPE_REPOSITORY (ID, CONTENT) VALUES (a7ca2377505d642f12b271-5c75-40d9-9374-8f708687b809, ?)
19:28:06.224 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - Releasing DB connection for transaction 4a848140-8dfb-4bf7-9c59-49e03dc6affe
19:28:06.287 [wisdom-system-executor-10] DEBUG c.zaxxer.hikari.pool.ProxyConnection - HikariPool-0 - Executed rollback on connection com.mysql.jdbc.JDBC4Connection@71673bd1 due to dirty commit state on close().
19:28:06.289 [wisdom-system-executor-10] DEBUG com.zaxxer.hikari.pool.PoolBase - HikariPool-0 - Reset (autoCommit, isolation) on connection com.mysql.jdbc.JDBC4Connection@71673bd1
19:28:06.290 [wisdom-system-executor-10] DEBUG org.modeshape.jcr.BackupService - Restoring documents from /tmp/restore-14763794530877862205647426883719/changes
19:28:06.290 [wisdom-system-executor-10] DEBUG org.modeshape.jcr.BackupService - Restored 0 documents from /tmp/restore-14763794530877862205647426883719/changes
19:28:06.290 [wisdom-system-executor-10] DEBUG org.modeshape.jcr.BackupService - clearing existing persistent store...
19:28:06.290 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - New transaction '5350f86b-62f8-4398-9854-d13c3b6347a2' started by ModeShape...
19:28:06.292 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - New DB connection allocated for tx '5350f86b-62f8-4398-9854-d13c3b6347a2'
19:28:06.292 [wisdom-system-executor-10] DEBUG o.m.p.relational.DefaultStatements - Removing all content from MODESHAPE_REPOSITORY
19:28:07.842 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - Received committed notification for transaction '5350f86b-62f8-4398-9854-d13c3b6347a2'
19:28:07.842 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - Committing the active connection for transaction 5350f86b-62f8-4398-9854-d13c3b6347a2 with the changes: {}
19:28:16.605 [wisdom-system-executor-10] DEBUG o.m.p.relational.RelationalDb - Releasing DB connection for transaction 5350f86b-62f8-4398-9854-d13c3b6347a2
19:28:16.606 [wisdom-system-executor-10] DEBUG com.zaxxer.hikari.pool.PoolBase - HikariPool-0 - Reset (autoCommit, isolation) on connection com.mysql.jdbc.JDBC4Connection@71673bd1
19:28:16.606 [wisdom-system-executor-10] DEBUG org.modeshape.jcr.BackupService - Completed restore of 'cloud-repository-test' repository from /tmp/restore-14763794530877862205647426883719
