Make logging on Tomcat use JDK14LoggerPlugin by default ------------------------------------------------------- Key: MODCLUSTER-185 URL: https://issues.jboss.org/browse/MODCLUSTER-185 Project: mod_cluster Issue Type: Feature Request Security Level: Public(Everyone can see) Affects Versions: 1.1.0.Final Environment: Windows 7 x64, Java 1.6.0_18-b07 32bit, Tomcat 6.0.29 + APR 1.1.20 + load-demo webapp jboss-logging-jdk.jar Implementation-Version: 2.1.1.GA jboss-logging-spi.jar Implementation-Version: 2.0.5.GA Reporter: Ruslan Gainutdinov Assignee: Paul Ferraro Priority: Minor Labels: logging, mod_cluster, tomcat Fix For: 1.1.1.Final Attachments: mod-cluster-listener-jdk-logging.patch I`ve added jboss-logging-jdk.jar jboss-logging-spi.jar mod_cluster.jar to Tomcat lib/ directory. However, when I start Tomcat, no messages from mod_cluster is displayed. By debugging I was able to understand what NullLoggerPlugin is used. Where is a code to initialize logging in Tomcat - org.jboss.modcluster.catalina.ModClusterListener.java:65 however, it is not working because org.jboss.logging.Logger.init() called before it. By default, system tries to load log4j plugin, which is not available in this environment. After that, it sets NullLoggerPlugin. To workaround this, I have added -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.jdk.JDK14LoggerPlugin to java options used when Tomcat is started. I propose fixing org.jboss.modcluster.catalina.ModClusterListener.java with patch (attaching in next comment).