User Activity

  • Modified a comment on discussion ejbca-develop on EJBCA, JEE PKI Certificate Authority

    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: <exclusions> <module name="org.apache.logging.log4j.api">...

  • Posted a comment on discussion ejbca-develop on EJBCA, JEE PKI Certificate Authority

    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">...

  • Posted a comment on discussion ejbca-develop on EJBCA, JEE PKI Certificate Authority

    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:...

  • Posted a comment on discussion ejbca-develop on EJBCA, JEE PKI Certificate Authority

    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

View All

Personal Data

Username:
omarsale
Joined:
2025-04-04 09:38:12.233000

Projects

  • No projects to display.

Personal Tools

MongoDB Logo MongoDB