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. This section outlines the steps needed to 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.
Debugging an upgrade
The startup log is important to help Alfresco Support diagnose any issues that might arise as a result of the upgrade.
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 log4.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.
Adding swap space in Linux
When running Alfresco in a Linux environment, in some circumstances, it may be necessary to add extra swap space.
Testing and debugging links
The <configRoot>/log4j.properties file lets you set the level of logging based on the amount of information you need.
This section lists issues that you may encounter when installing Alfresco and suggests possible remedies.
Troubleshooting an upgrade
This section provides help for diagnosing and resolving any issues that might arise as a result of an upgrade.
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 may need to tune the client operating system parameters so that it can handle a higher rate of outbound TCP connections.
This error message relates to the IP address or hostname that has been supplied for binding.