Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

Tomas Gustavsson — Mon, 07 Apr 2025 08:29:52 -0000

Hi Omar,

That sounds like a question you should ask in the forum. For the benefit of the whole Community.
Unless you are a support customer, and have access to the Enterprise support system of course.

Cheers,
Tomas

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

omar salek — Sat, 05 Apr 2025 11:31:04 -0000

Hi Tomas,

Thank you for your response.

i found the same bug on Github :

https://github.com/Keyfactor/ejbca-ce/issues/821

we’d like to confirm if any of the following approaches are valid or recommended. Your input would be greatly appreciated:

Option 1 – Exclude Log4j API using Kubernetes ConfigMap
We’re deploying EJBCA in a Kubernetes environment. One idea is to mount a volume with a custom META-INF/jboss-deployment-structure.xml file that includes:

xml
Copier
Modifier
<exclusions>
<module name="org.apache.logging.log4j.api">
</module></exclusions>
This allows us to exclude the Log4j 2 API temporarily to bypass the conflict. After the upgrade, we could remove the exclusion to restore full logging functionality.
Would this approach be safe, or could it cause instability or log loss during the upgrade process?

Option 2 – Upgrade in Two Steps (via 8.3.2)
Would it be possible to first upgrade to an intermediate version like EJBCA 8.3.2, and then proceed to 9.0.0?
If so, does this path avoid the Log4j issue, and is it a supported upgrade method?

Option 3 – Wait for a Future Release
We noticed that EJBCA Community 9.1.1 has been released recently.
Do you know if this version addresses the Log4j conflict? If not, will an upcoming release (e.g., 9.2 or 9.3) include a permanent fix?

Thanks again for your time and help. Looking forward to your feedback so we can move forward safely with the upgrade.

Best regards,
Omar Salek

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

Tomas Gustavsson — Fri, 04 Apr 2025 18:39:23 -0000

You can find information about this at GitHub there the forum is now located. You can find a link to GitHub Discussions on the web page. https://www.ejbca.org/engage/

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

omar salek — Fri, 04 Apr 2025 16:06:35 -0000

2025-04-04 16:03:18,443+0000 ERROR [org.ejbca.core.ejb.upgrade.UpgradeSessionBean] (EJB default - 1) 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 'org.jboss.logmanager.log4j2@1.1.2.Final' @c0c07e4; org.apache.logging.log4j.core.Logger is in unnamed module of loader 'deployment.ejbca.ear' @5c982fcd): 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 'org.jboss.logmanager.log4j2@1.1.2.Final' @c0c07e4; org.apache.logging.log4j.core.Logger is in unnamed module of loader 'deployment.ejbca.ear' @5c982fcd)

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

omar salek — Fri, 04 Apr 2025 10:30:26 -0000

Hello,

We are currently performing an upgrade of EJBCA from version 6.10.1 to 9.0.0. During the post-upgrade process, we encountered an error related to compatibility issues between Log4j and the logging system, as both seem to be in use simultaneously. Despite not finding Log4j references in the standalone.xml, we would like to disable or resolve this conflict.

Could you please provide guidance on how to deactivate Log4j or suggest any alternative solutions to address this issue?

Thank u

How to renew client Certificate to access CAAdmin console in EJBCA version 3.9.7

Tomas Gustavsson — Thu, 25 Jan 2024 13:34:19 -0000

Dev: Please create a new issue in GitHub.
https://github.com/Keyfactor/ejbca-ce/discussions

Deleting these.

How to renew client Certificate to access CAAdmin console in EJBCA version 3.9.7

Dev — Thu, 25 Jan 2024 11:46:43 -0000

i used command ant -q clean deployear

How to renew client Certificate to access CAAdmin console in EJBCA version 3.9.7

Dev — Thu, 25 Jan 2024 11:45:36 -0000

11:10:44,325 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ejbca.ear")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.EjbcaDS"],
"WFLYCTL0180: Services with missing/unavailable dependencies" =>
"jboss.persistenceunit.\"ejbca.ear#ejbca\" is missing [jboss.naming.context.java.EjbcaDS",
"jboss.persistenceunit.\"ejbca.ear#ejbca\".FIRST_PHASE is missing [jboss.naming.context.java.EjbcaDS]"
]
}
11:10:44,360 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "ejbca.ear" (runtime-name : "ejbca.ear")
11:10:44,364 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.naming.context.java.EjbcaDS (missing) dependents: [service jboss.persistenceunit."ejbca.ear#ejbca".FIRST_PHASE, service jboss.persistenceunit."ejbca.ear#ejbca"]
WFLYCTL0448: 629 additional services are down due to their dependencies being missing or failed

ERROR DEPLOYEAR

Tomas Gustavsson — Fri, 19 Jan 2024 07:58:43 -0000

Hi,
Can you post this to the GitHub discussions. With some more details such as what version of EJBCA you are using, what version of application server, version of Java, and such.
https://github.com/Keyfactor/ejbca-ce/discussions

ERROR DEPLOYEAR

AbdoulKadri Mossi — Thu, 18 Jan 2024 16:40:21 -0000

how to fix this error

2024-01-16 15:23:40,022 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Read persistence.xml for ejbca
2024-01-16 15:23:41,611 INFO [org.jipijapa] (MSC service thread 1-1) JIPIORMV6020260: Second level cache enabled for ejbca.ear#ejbca
2024-01-16 15:23:41,702 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool -- 170) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller'
2024-01-16 15:23:42,243 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment ejbca.ear
2024-01-16 15:23:42,307 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment edition-specific-ejb.jar
2024-01-16 15:23:42,309 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment doc.war
2024-01-16 15:23:42,309 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment ejbca-ejb.jar
2024-01-16 15:23:42,318 WARN c

2024-01-16 15:23:42,318 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class org.ejbca.util.ServiceControlFilter in Module "deployment.ejbca.ear" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/ejbca/util/ServiceControlFilter (Module "deployment.ejbca.ear" from Service Module Loader): javax/servlet/Filter
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1095)
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:351)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:276)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:79)
at org.jboss.modules.Module.loadModuleClass(Module.java:765)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:192)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:398)
at org.jboss.as.ee@30.0.0.Final//org.jboss.as.ee.utils.ClassLoadingUtils.loadClass(ClassLoadingUtils.java:26)
at org.jboss.as.ee@30.0.0.Final//org.jboss.as.ee.utils.ClassLoadingUtils.loadClass(ClassLoadingUtils.java:19)
at org.jboss.as.ee@30.0.0.Final//org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:67)
at org.jboss.as.ee@30.0.0.Final//org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:60)
at org.jboss.as.server@22.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:171)
at org.jboss.msc@1.5.2.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1617)
at org.jboss.msc@1.5.2.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1580)
at org.jboss.msc@1.5.2.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1438)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
at java.base/java.lang.Thread.run(Thread.java:834)

Recent posts to ejbca-develop

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

Urgent: Compatibility Issue During EJBCA Upgrade (Log4j Conflict)

How to renew client Certificate to access CAAdmin console in EJBCA version 3.9.7

How to renew client Certificate to access CAAdmin console in EJBCA version 3.9.7

How to renew client Certificate to access CAAdmin console in EJBCA version 3.9.7

ERROR DEPLOYEAR

ERROR DEPLOYEAR