commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LOGGING-96) [logging] Include class loader information when LogFactoryImpl throws LogConfigurationException.
Date Tue, 29 Dec 2009 16:52:29 GMT

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

Dennis Lundberg updated LOGGING-96:
-----------------------------------

    Fix Version/s: 1.1.0

> [logging] Include class loader information when LogFactoryImpl throws LogConfigurationException.
> ------------------------------------------------------------------------------------------------
>
>                 Key: LOGGING-96
>                 URL: https://issues.apache.org/jira/browse/LOGGING-96
>             Project: Commons Logging
>          Issue Type: Improvement
>    Affects Versions: 1.0.4
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Stephen Smith
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> LogFactoryImpl#getLogConstructor throws a LogConfigurationException when the
> same class is detected in multiple class loaders. The error message is as follows:
> "Invalid class loader hierarchy. You have more than one version of <class-name>
> visible, which is not allowed."
> We could improve the usefulness of the error message by including classloader
> details such as ClassLoader#getClass, etc. It would greatly reduce the time
> spent hunting down multiple copies of Commons Logging (which can frequently
> occur when deploying to application servers such as JBoss and WebLogic, as they
> often have a version of Commons Logging stowed away in their own class path).

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


Mime
View raw message