Adjusting Granularity of Application and Container Logs
log4j can be adjusted for both the Kuali application (KFS / KR) and the Tomcat servlet container for each environment.
KFS
The following files can be edited to adjust how fine a level of logging you want in the KFS environments
/etc/tomcat6/log4j.properties for the Tomcat servlet container
/srv/uconn_configs/kfs-config/j2ee/<dev/prd>/kfs/log4j.properties for the KFS application
These files should be BACKED UP before making any changes to them, and all changes should be tested in a non-production environment before being attempted in PRD.
KR
The following files can be edited to adjust how fine a level of logging you want in the KR environments
/etc/tomcat6/log4j.properties for the Tomcat servlet container
/srv/uconn_configs/rice-config/log4j.properties for the RICE application
These files should be BACKED UP before making any changes to them, and all changes should be tested in a non-production environment before being attempted in PRD.
ROOT access is required to change the Tomcat logging file.
The application (and container) must be restarted for changes to take effect.
Additional values can be added to the application log4j file to provide output about certain classes/actions.
Care must be taken when setting values to DEBUG level, to ensure that the logs don't fill up too quickly and fill the /VAR filesystem (this will cause the application to halt until the fs is cleared).