[jira] Updated: (LOGGING-14) [logging] LogConfigurationException double wrapped

["Dennis Lundberg (JIRA)" <ji...@apache.org>]

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

Dennis Lundberg updated LOGGING-14:
-----------------------------------

    Fix Version/s: 1.1.0

> [logging] LogConfigurationException double wrapped
> --------------------------------------------------
>
>                 Key: LOGGING-14
>                 URL: https://issues.apache.org/jira/browse/LOGGING-14
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: 1.0.4
>         Environment: Operating System: Windows 2000
> Platform: PC
>            Reporter: Bill Zwicky
>             Fix For: 1.1.0
>
>
> 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); }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.