[LOGGING-96] [logging] Include class loader information when LogFactoryImpl throws LogConfigurationException.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.4
• Fix Version/s: 1.1.0

Environment

Operating System: other
Platform: Other

• Bugzilla Id: 36041
• Assignee: Unassigned
• Reporter: Stephen Smith
• Created: 05/Aug/05 22:19
• Updated: 29/Dec/09 16:52
• Resolved: 29/Dec/09 16:52

Description

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).