Issues upgrading to ejbca 9.0.0

[mdmetsotto]

We have installed ejbca ce 9.0.0 and restored database from our old server, which has ejbca ce version 6.15.2.6. We can access the adminweb on the new installation, but it's complaining about the post-upgrade not being done and when we try to go to the System Upgrade page and press "Start post-upgrade", nothing happens. The page says that "Effective version of data" is 6.10.1, which does not match the real version on the old server. We get below errors in the log when pressing "Start post-upgrade". Any ideas or advices how to get forward? The cli doesn't seem to have an option to run the post-upgrade. ejbca 9.0.0 adminweb is also really slow, not sure if it's caused by the old database or something else.

2025-02-13 07:13:55,415 ERROR [org.ejbca.core.ejb.upgrade.UpgradeSessionBean] (EJB default - 2) Unexpected error from post-upgrade: java.lang.ClassCastException: class org.jboss.logmanager.log4j.JBossLogger cannot be cast to class org.apache.logging.log4j.core.Logger (org.jboss.logmanager.log4j.JBossLogger is in unnamed module of loader '[email protected]' @875b60e; org.apache.logging.log4j.core.Logger is in unnamed module of loader 'deployment.ejbca.ear' @17f77836): jakarta.ejb.EJBException: java.lang.ClassCastException: class org.jboss.logmanager.log4j.JBossLogger cannot be cast to class org.apache.logging.log4j.core.Logger (org.jboss.logmanager.log4j.JBossLogger is in unnamed module of loader '[email protected]' @875b60e; org.apache.logging.log4j.core.Logger is in unnamed module of loader 'deployment.ejbca.ear' @17f77836)

Caused by: java.lang.ClassCastException: class org.jboss.logmanager.log4j.JBossLogger cannot be cast to class org.apache.logging.log4j.core.Logger (org.jboss.logmanager.log4j.JBossLogger is in unnamed module of loader '[email protected]' @875b60e; org.apache.logging.log4j.core.Logger is in unnamed module of loader 'deployment.ejbca.ear' @17f77836)

[mike-agrenius-kushner]

Hi,

What version of WF are you running 9.0 on?

Cheers,
Mike

[mdmetsotto]

Hi,

We have WildFly 32.

Cheers,
Otto

[primetomas]

We are looking into if this may be an issue in EJBCA 9. You can likely bypass the issue by upgrading to EJBCA 8 first, and then move to 9. Because the upgrade from 8 to 9 does not require a post-upgrade.