What is the suggested log configuration for a production system?

To troubleshoot installation issues, the default log4j configuration is set to DEBUG for all systems. This can cause the log files to become quite large. Once your system is successfully installed and in use, you should drop the log levels down to INFO for most systems.

The log levels are defined in /opt/collabnet/teamforge/runtime/jboss/server/default/conf/log4j.xml. All instances of "DEBUG" should be changed to "INFO". Some services, such as the soap endpoints, are set to level WARN; these can stay set to WARN.

The perl -pie invocation can be used to do this in one command, which will create log4j.xml.bak:

perl -pi'.bak' -e 's/"DEBUG"/"INFO"/' /opt/collabnet/teamforge/runtime/jboss/server/default/conf/log4j.xml

After changing, restart the application via 'service collabnet restart'. If the runtime is rebuilt, this process will need to be redone.