Uploaded image for project: 'Commons Logging'
  1. Commons Logging
  2. LOGGING-96

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

    Details

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

      Operating System: other
      Platform: Other

    • Bugzilla Id:
      36041

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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              steve@stephen-smith.co.uk Stephen Smith
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: