All Products
Search

This Product

    Enterprise Distributed Application Service:Use logs for troubleshooting

    Document Center

    Enterprise Distributed Application Service:Use logs for troubleshooting

    Last Updated:Mar 11, 2026

    Enterprise Distributed Application Service (EDAS) generates several log files at runtime. Use these logs to identify and resolve application errors.

    Log files

    The following table lists EDAS log files in recommended troubleshooting order. Start with catalina.out for most issues.

    Log filePathWhen to check
    Tomcat server log/home/admin/taobao-tomcat-production-xxxx/logs/catalina.outCheck first. Records application exceptions and Tomcat server errors. This is the primary log for development and runtime troubleshooting.
    Tomcat localhost log/home/admin/taobao-tomcat-production-xxxx/logs/localhost.log.xxxCheck when catalina.out does not reveal the cause, or the error is difficult to identify. Confirms whether the application started successfully.
    Configuration client log/home/admin/configclient/logs/config.client.logCheck whether service publish and subscribe operations succeeded. Search for the keywords Register-ok and Publish-ok.
    High-speed Service Framework (HSF) log/home/admin/logs/hsf/hsf.logCheck when an HSF service call throws an exception. Contains HSF service invocation details.

    In the paths above, xxxx represents the version identifier in your Tomcat installation directory. Replace it with the actual directory name on your instance.

    Troubleshoot application container errors

    To diagnose errors in the application container, follow these steps:

    1. Open /home/admin/taobao-tomcat-production-xxxx/logs/catalina.out and look for exception stack traces or error messages.

    2. If catalina.out does not reveal the issue, check /home/admin/taobao-tomcat-production-xxxx/logs/localhost.log.xxx for startup errors or additional context.

    3. Locate the first Tomcat-related error in the logs. Fix that error first, then restart the application. After the restart, check the logs again to verify whether additional errors remain.

    Fix errors one at a time, starting with the earliest error in the log. Later errors are often caused by the first failure, so resolving the root cause may clear multiple issues at once.