By default, ATG sends all log events to two log listener components: /atg/dynamo/service/logging/LogQueue (which directs output to log files) and /atg/dynamo/service/logging/ScreenLog (which directs output to the console screen). Logging to the screen can cause performance problems on a production site. Note that JBoss and Tomcat extend ExternalLogSystemLogListener and do not use the PrintStreamLogger, which is used by ScreenLog to redirect output to the console screen.
It is recommended that you redirect console logging to a file to prevent loss of information. When creating the file, it is helpful to script the console log file name to contain the current time stamp, such as console_2013-03-03_16-39-22.log. Refer to your Web application documentation for information on redirecting console log information to a file.
If you want to disable logging entirely, or specify different logging levels, you can do that in the GLOBAL.properties file. For example:
loggingError=true
loggingWarning=true
loggingInfo=true
loggingDebug=false
The loggingDebug log generates large numbers of messages, which can impair performance, so loggingDebug should be set to false on a live site. You still have the option of overriding the global settings for a specific component. For example, if loggingDebug is set to false in the GLOBAL.properties file, you can still enable it for an individual component by setting that component’s loggingDebug property to true.
See the Logging and Data Collection chapter of the Platform Programming Guide for more information.
