Setting log levels
The log4j.properties file lets you configure logging levels to provide debugging information when troubleshooting. To set up logging policies, you must prepend log4j.logger to the class name you want to log to, and set the logging level. You can set the log level dynamically using the JMX client.
Use this information to help troubleshoot your Alfresco installation.
Using the Node Browser
Use Node Browser in the Admin Console or in Share Admin Tools as an debugging aid to browse the raw Alfresco repository structure. This feature is intended for developers responsible for customizing the application.
Debugging an Alfresco installation
When developing add-ins, fixing bugs, or changing Alfresco from the source code, it is helpful to debug an instance of Alfresco running on a standard application server. You can configure Alfresco and Eclipse to provide a real-time view of the server and to troubleshoot issues by stepping through the code line by line.
Handling a higher rate of outbound TCP connections
If you are using the Alfresco Web Services API on a Windows client and frequently see errors such as java.net.BindException: Address already in use: connect in the client application, you might need to tune the client operating system parameters so that it can handle a higher rate of outbound TCP connections.