commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Benedict <>
Subject Re: [LANG] 2.4: ExceptionUtils.getFullStackTrace()
Date Thu, 05 Nov 2009 17:57:15 GMT
Exception traces can also be cyclic. An exception may set itself as
the root cause, or A -> B -> A.

On Thu, Nov 5, 2009 at 11:21 AM, Henri Yandell <> wrote:
> I think the issue is that if you print the nested exception and keep
> going, you'll get a lot of duplicates as the nested exception will
> print all its children, then you'll go ahead and loop into the child.
> Looking at the source to getThrowableList - it seems to me that the
> throwable list is top down (ie: exception received and then into its
> causes and its causes causes etc) so much like your comment on
> reverse.
> On Wed, Nov 4, 2009 at 2:08 PM, Charles Deal <> wrote:
>> The getFullStackTrace() method javadoc states "A way to get the entire
>> nested stack-trace of an throwable....".  However, after gathering the
>> nested Throwables, it performs a check while processing the array of
>> Throwables that causes it to abort before it renders the nested
>> stacktraces.
>> My question is: Should the if check be there?  Why go through the trouble of
>> getting the nested Throwables if you are going to short-circuit the
>> rendering loop?  I suppose it is possible that the intent was to iterate the
>> list in REVERSE and stop the rendering when you hit the Throwable that had a
>> root Cause.
>> Any thoughts?  I ended up capturing the getFullStackTrace method and removed
>> the if check within the loop and got exactly what I was looking for.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message