DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36041>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36041 Summary: Include class loader information when LogFactoryImpl throws LogConfigurationException. Product: Commons Version: 1.0.4 Platform: Other OS/Version: other Status: NEW Keywords: ErrorMessage Severity: enhancement Priority: P2 Component: Logging AssignedTo: commons-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] 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). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
