1 Reply Latest reply on May 30, 2008 7:29 PM by 666705

    log4j:ERROR Could not instantiate configurator

    666705
      I use
      -Dlog4j.configuratorClass=mypackage.Log4jConfigurator
      java option in startWeblogic command file
      to read changes in log4j-config.xml.
      After that I have in console.log
      og4j:ERROR A "mypackage.Log4jConfigurator" object is not assignable to a "org.apache.log4j.spi.Configurator" variable.
      log4j:ERROR The class "org.apache.log4j.spi.Configurator" was loaded by
      log4j:ERROR [weblogic.utils.classloaders.GenericClassLoader@544b02 finder: weblogic.utils.classloaders.CodeGenClassFinder@a0e9d7 annotatio
      n: consoleapp@] whereas object of type
      log4j:ERROR "mypackage.Log4jConfigurator" was loaded by [sun.misc.Launcher$AppClassLoader@12498b5].
      log4j:ERROR Could not instantiate configurator [mypackage.Log4jConfigurator].

      Could anybody help?
        • 1. Re: log4j:ERROR Could not instantiate configurator
          666705
          Did you get a resolution? I have a similar problem with a different object, org.apache.log4j.spi.TriggeringEventEvaluator, which has been loaded by the Weblogic consoleapp. I am running in a standalone server configuration -- admin and application server are the same. Also, using exploded directories.

          Is there a way to prevent the WebLogic classloader from loading its version from the consoleapp?