Nuxeo logging is compliant with common Java logging frameworks Log4J, SLF4J and JUL.
Logging in Nuxeo is configured through a Log4J xml file:
- $NUXEO_HOME/lib/log4j.xml (for Tomcat)
- $NUXEO_HOME/server/default/conf/jboss-log4j.xml (for Nuxeo 5.2+ with JBoss)
- $NUXEO_HOME/server/default/conf/log4j.xml (for Nuxeo 5.1 with JBoss)
Editing that file, you can set the logging rules (log level per file and component, files rotation, ...).
Related pages:
- Log4J
- How to change the JBoss log files rotation
- Where are the log and configuration files in Windows?
Tomcat specific
 | The following information is for debug purpose, it may have impacts on performance and logging files size |
$NUXEO_HOME/conf/logging.properties has no effect; you can safely remove it.
Because Tomcat uses java.util.logging of which Log4J is not aware, Tomcat logs (org.apache.catalina.*) have to be redirected to Apache Commons Logging (compliant with Log4J).
Nuxeo provides a bridge for that redirection (in org.nuxeo.common.logging.JavaUtilLoggingHelper) with a default threshold set at INFO level. You can customize it by adding into nuxeo.conf:
But that redirection is only available after Nuxeo Framework initialization whereas most of the startup logs from org.apache.catalina happen before (when the redirection is not yet active).
So, if you want to see Catalina startup messages, you must also:
- go on Tomcat 6 download page, then "Quick Navigation", "Browse", "bin", "extras"
- download tomcat-juli-adapters.jar into $NUXEO_HOME/lib/
- download tomcat-juli.jar into $NUXEO_HOME/bin/ (replace the existing one)