axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Commented: (AXIS2-3374) support logging full stack traces in log
Date Wed, 12 Mar 2008 17:18:46 GMT


Davanum Srinivas commented on AXIS2-3374:


i believe we are getting better at this...please try latest svn/nightly and let us know if
there are any more specific places if we missed.


> support logging full stack traces in log
> ----------------------------------------
>                 Key: AXIS2-3374
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>            Reporter: Mark Anderson
>            Priority: Minor
> At least the Sun JDK truncates stack traces when nested, and Sun at least seems
> totally uninterested in addressing this:
> Because axis typically has multiple levels of exception catching, this causes
> the real cause to be lost.
> The top-level exception might be:
> [java] <Exception>org.apache.axis2.AxisFault:
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> [java] at org.apache.axis2.AxisFault.makeFault(
> [java] at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(

> ...
> but the interesting stuff is nested 4 or 5 levels down, and there the JDK just
> says something like "48 more".
> I think the only work around is to manually navigate down each nested exception
> and log them yourself.
> This should be a configurable thing for log files.
> Of course you'll want to have some self-protection for (near-)infinite loop cases,
> which is presumably why Sun has this hard-coded behavior to begin with.
> -mda

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message