Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361319 - Log initialization does not catch correct exceptions on all jvms
Summary: Log initialization does not catch correct exceptions on all jvms
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.5.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 7.5.x   Edit
Assignee: Jan Bartel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-18 21:24 EDT by Jan Bartel CLA
Modified: 2011-10-18 21:29 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Bartel CLA 2011-10-18 21:24:32 EDT 
The Log.initialized() method catches NoClassDefFound and Exception when trying to find if Slf4j is on the classpath or not. Unfortunately, sometimes a different Throwable is thrown instead. Eg on Android, it is a VerifyError.

Change to catch Throwable and rethrow if it is ThreadDeath.
Comment 1 Jan Bartel CLA 2011-10-18 21:29:11 EDT 
Fixed for 7.4.0.