[LOGGING-14] [logging] LogConfigurationException double wrapped

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.4
• Fix Version/s: 1.1.0

Environment

Operating System: Windows 2000
Platform: PC

• Bugzilla Id: 35112
• Assignee: Unassigned
• Reporter: Bill Zwicky
• Created: 28/May/05 06:23
• Updated: 29/Dec/09 16:12
• Resolved: 29/Dec/09 16:12

Description

LogFactoryImpl.getLogConstructor() double-wraps when it throws
LogConfigurationException. In other words, when it throws
LogConfigurationException, it wraps that exception in another
LogConfigurationException. In fact, the full message is:

org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
java.lang.NullPointerException (Caused by java.lang.NullPointerException)
(Caused by org.apache.commons.logging.LogConfigurationException:
java.lang.NullPointerException (Caused by java.lang.NullPointerException))

Feel free to track that mess down, but this report is just for this one instance
of wrapping.

The wrapping occurs on line 397. You can fix it either by ensuring the "throw
new" calls are outside the "catch Throwable", or you can add an extra catch:

catch (LogConfigurationException ex)

{ throw ex; }

catch (Throwable t)

{ throw new LogConfigurationException(t); }