axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Anderson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-3374) support logging full stack traces in log
Date Thu, 29 Nov 2007 00:00:43 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Anderson updated AXIS2-3374:
---------------------------------

    Description: 
At least the Sun JDK truncates stack traces when nested, and Sun at least seems
totally uninterested in addressing this:
   http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4775147

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(AxisFault.java:417)
[java] at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:156)

...

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


  was:
At least the Sun JDK truncates stack traces when nested, and Sun at least seems
totally uninterested in addressing this:
   http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4775147

This causes problems with axis which seems to have multiple levels of nesting.
So 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(AxisFault.java:417)
[java] at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:156)

...

but the interesting stuff is nested 4 or 5 levels down.
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



> support logging full stack traces in log
> ----------------------------------------
>
>                 Key: AXIS2-3374
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3374
>             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:
>    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4775147
> 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(AxisFault.java:417)
> [java] at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:156)

> ...
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message