Bug 56291 - EnhancdedThrowableRender does not handle java.lang.NoClassDefFoundError's
Summary: EnhancdedThrowableRender does not handle java.lang.NoClassDefFoundError's
Status: NEW
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.2.17
Hardware: Other Linux
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
Depends on:
Reported: 2014-03-20 06:07 UTC by Steve
Modified: 2014-03-20 06:07 UTC (History)
0 users

StackTrace. (2.21 KB, text/plain)
2014-03-20 06:07 UTC, Steve

Note You need to log in before you can comment on or make changes to this bug.
Description Steve 2014-03-20 06:07:42 UTC
Created attachment 31414 [details]

We currently run an environment with Websphere 7.0 backends ( IBM 1.6 JDK ) and Tomcat 6 front ends ( Oracle 1.6 jdk) and we have just had a case where the backend has thrown an exception which has bubbled up to our web servers, and has been logged with the EnhancedThrowableRender. 

This has resulted in a java.lang.NoClassDefFoundError from the findClass method of the EnhancedThrowableRender,  as this is an Error rather than an Exception this has bypassed the catch Exception block of the doRenderMethod, so rather than defaulting back to the DefaultThrowableRender it has crashed the application. 

I would have expected that the doRenderMethod should be catching Throwable rather than Exception, or at least the NoClassDefFoundError.