There are three primary troubleshooting tools you will become intimately familiar with: Log4j, your favorite Java debugger, and the Alfresco Node Browser. There are other, less-frequently used tools and techniques that will be discussed when the time is right.
Most of you are already familiar with this common logging tool, so not a lot of discussion is needed. For everyone else, here are the basics. The verbosity of the log output, the specific classes being logged, and other logging settings are controlled by the log4j.properties
file located in WEB-INF|classes. This is one file distributed with Alfresco that is OK to touch. For example, if you are testing out some server-side JavaScript, you might want to change the JavaScript-related logger from error to debug like this:
log4j.logger.org.alfresco.repo.jscript=DEBUG
If you want to add your own logger for one of your own Java classes, add a new logger to the end of the file like this:
log4j.logger.com.someco=DEBUG
Then,...