Integration Server 10.5 | Integration Server Administrator's Guide | Debugging Service Exceptions Using the Error Log | Interpreting the Error Log | Understanding the Stack Trace
 
Understanding the Stack Trace
Exceptions often contain other exceptions nested within them. The extent to which the Stack Trace column reports the call sequence leading to the exceptions depends on the setting you select for the watt.server.deprecatedExceptionLogging parameter, as follows:
*If this parameter is set to false (detailed exception logging), the error log's Stack Trace column shows the innermost stack trace (that is, the stack trace that points to the source of the problem).
*If this parameter is set to true (basic exception logging), the stack trace is often truncated and the cause of the exception becomes more difficult to trace. For this reason, Software AG recommends that you do not set this parameter to true unless you are executing services that catch exceptions and do not rethrow them.