Provider Log4jServletContainerInitializer not found

[theblur05]

I was hoping someone might be able to help me figure out this deployment error. I am using Jboss eap 6.2 and have a webservice that uses a library which has a log4j2 logger. This library uses log4j classes only available in the log4j 2.0-rc1 jars. During deployment of the war, the webservice creates and initializes this library, which in turn, initializes log4j. Immediately jboss throws the following exception:

09:10:09,340 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."webservice.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."webservice.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "webservice.war"

    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45]

    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]

Caused by: java.util.ServiceConfigurationError: javax.servlet.ServletContainerInitializer: Provider org.apache.logging.log4j.core.web.Log4jServletContainerInitializer not found

    at java.util.ServiceLoader.fail(ServiceLoader.java:239) [rt.jar:1.8.0_45]

    at java.util.ServiceLoader.access$300(ServiceLoader.java:185) [rt.jar:1.8.0_45]

    at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:372) [rt.jar:1.8.0_45]

    at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) [rt.jar:1.8.0_45]

    at java.util.ServiceLoader$1.next(ServiceLoader.java:480) [rt.jar:1.8.0_45]

    at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:108)

    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

    ... 5 more

I have expanded the war and confirmed that the log4j-core and log4j-api jars are present, and org.apache.logging.log4j.core.web.Log4jServletContainerInitializer.class is present in the log4j-core jar. Does jboss require a later version of the log4j library? As far as I can tell, Log4jServletContainerInitializer isn't available in later releases of log4j.

[lylewang]

EAP 6 supports log4j 1.x, currently log4j 2.x is not supported as far as I know.

You can try exclude JBoss provided log4j modules via " jboss-deployment-structure.xml" : Class Loading in AS7 - JBoss AS 7.2 - Project Documentation Editor

Something like this: http://stackoverflow.com/questions/17136035/how-to-enable-a-custom-log4j-with-jboss-as-7-1

Or this one: Configure Jboss eap 6.2 to use log4j2

But I haven't tried these as they're not officially supported way.

By the way, JDK 8 is only supported on EAP 6.3.3+, not EAP 6.2.

[theblur05]

Thanks for the helpful info Lyle, as a newb to jboss, I wasn't even aware JDK 8 wasn't supported by EAP6.2. As for the classloading issue, I did stumble upon and try the solutions provided in those links. That didn't fix it. So, I fired up remote debugging and found that the library being imported by my webservice, is adding the log4j core and api jars to the class loader urls list. The resulting Classloading urls looks something like: [JBOSS_HOME/jboss-modules.jar, PATH_TO_LOG4J/log4j-api-2.0-rc1.jar, PATH_TO_LOG4J/log4j-api-2.0-rc1.jar].

Loading these two jars (obviously) overrides default jboss classloading, resulting in the error in the original post. If I remove the code that dynamically loads the jars, the deployment error goes away.

Could anyone shed light on why a jboss deployment would fail after runtime classloading as occurred.

[jamezp]

Are the log4j2 JAR's in your WAR/WEB-INF/lib directory? If so I'm not sure why they wouldn't be accessible.

JBoss EAP and WildFly will add a log4j 1.x dependency to all deployments. A log4j2 dependency is not provided so as long as those dependencies are in your WAR I'm not sure why it wouldn't work.

--

James R. Perkins