Can container running with EJBCA 8.0 CE and H2 DB be replicated

[merryo11]

Hi ,
I have a UAT environment where I setup EJBCA 8.0 with H2 DB container. Since I have created few CAs, Cert. and end entity profiles and my SSL is also expiring how can I renew the SSL on it.

I tired to create a 2nd container with H2 DB whose DB I imported from the previous container and it started well but the DB comes up with read only mode and not allowing me to do any write operations but can read/search all the data of previous container.

Can any one guide how can I pass through this.

The command used for 2nd container using H2 DB of 1st container.

docker run -it -p 81:8080 -p 444:8443 --name uat-pki-lab-11072025_1 -h uat.pkilab.com -e TLS_SETUP_ENABLED="true" -e PASSWORD_ENCRYPTION_KEY="test" -e CA_KEYSTOREPASS="test" -e EJBCA_CLI_DEFAULTPASSWORD="test" -e ADMINWEB_ACCESS="true" -e LOG_LEVEL_APP_WS_TRANSACTIONS="DEBUG" -e LOG_LEVEL_APP="DEBUG" -v /tmp/server.jks:/mnt/external/secrets/tls/ks/server.jks -v /tmp/server.storepasswd:/mnt/external/secrets/tls/ks/server.storepasswd -v /tmp/truststore.jks:/mnt/external/secrets/tls/ts/truststore.jks -v /tmp/ejbcadb.mv.db:/mnt/persistent/ejbcadb.mv.db keyfactor/ejbca-ce:8.0.0

Log Error:
_2025-07-11 13:38:20,853+0000 WARN [com.arjuna.ats.arjuna] (default task-3) ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< 0:ffffac110002:7fecbb77:6871121c:136, org.wildfly.transaction.client.AbstractTransaction$AssociatingSynchronization@59437cc5 >: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute statement
......
Caused by: org.hibernate.exception.GenericJDBCException: could not execute statement
at [email protected]//org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47)
at [email protected]//org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:113)
at [email protected]//org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:99)
at [email protected]//org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:178)
at [email protected]//org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3377)
at [email protected]//org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:3250)
at [email protected]//org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3651)
at [email protected]//org.hibernate.action.internal.EntityUpdateAction.execute(EntityUpdateAction.java:146)
at [email protected]//org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:604)
at [email protected]//org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:478)
at [email protected]//org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:356)
at [email protected]//org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:39)
at [email protected]//org.hibernate.internal.SessionImpl.doFlush(SessionImpl.java:1472)
... 139 more
Caused by: org.h2.jdbc.JdbcSQLException: The database is read only; SQL statement:
update CryptoTokenData set lastUpdate=?, rowProtection=?, rowVersion=?, tokenData=?, tokenName=?, tokenProps=?, tokenType=? where id=? and rowVersion=? [90097-197]
at [email protected]_XF01213_BUILD2//org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
at [email protected]_XF01213_BUILD2//org.h2.message.DbException.get(DbException.java:179)
at [email protected]_XF01213_BUILD2//org.h2.message.DbException.get(DbException.java:155)
at [email protected]_XF01213_BUILD2//org.h2.message.DbException.get(DbException.java:144)
at [email protected]_XF01213_BUILD2//org.h2.engine.Database.checkWritingAllowed(Database.java:1989)
at [email protected]_XF01213_BUILD2//org.h2.table.Table.checkWritingAllowed(Table.java:1201)
at [email protected]_XF01213_BUILD2//org.h2.engine.User.hasRight(User.java:114)
at [email protected]_XF01213_BUILD2//org.h2.engine.User.checkRight(User.java:100)
at [email protected]_XF01213_BUILD2//org.h2.command.dml.Update.update(Update.java:97)
at [email protected]_XF01213_BUILD2//org.h2.command.CommandContainer.update(CommandContainer.java:102)
at [email protected]_XF01213_BUILD2//org.h2.command.Command.executeUpdate(Command.java:261)
at [email protected]_XF01213_BUILD2//org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:199)
at [email protected]_XF01213_BUILD2//org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:153)
at [email protected]//org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeUpdate(CachedPreparedStatement.java:121)
at [email protected]//org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:537)
at [email protected]//org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:175)
... 148 more
_

[merryo11]

With some further R&D I found that it was user permission which is making the DB right only. I changed the user rights using chown command with proper user and it started working.