5 Replies Latest reply on Jan 18, 2003 7:57 PM by richardberger

    Problems starting

    vpease

      I have a Winxp Pro system.
      i just expand the distribution and the run.bat give me this error:

      log4j:ERROR Could not instantiate class [org.jboss.logging.log4j.ConsoleAppender].
      java.lang.ClassNotFoundException: org.jboss.logging.log4j.ConsoleAppender
      at java.net.URLClassLoader$1.run(Unknown Source)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.net.URLClassLoader.findClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClassInternal(Unknown Source)
      at java.lang.Class.forName0(Native Method)
      at java.lang.Class.forName(Unknown Source)
      at org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:301)
      at org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:116)
      at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:612)
      at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:595)
      at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:502)
      at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:410)
      at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:309)
      at org.apache.log4j.PropertyWatchdog.doOnChange(PropertyConfigurator.java:665)
      at org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:80)
      at org.apache.log4j.helpers.FileWatchdog.(FileWatchdog.java:49)
      at org.apache.log4j.PropertyWatchdog.(PropertyConfigurator.java:657)
      at org.apache.log4j.PropertyConfigurator.configureAndWatch(PropertyConfigurator.java:373)
      at org.jboss.logging.Log4jService.start(Log4jService.java:111)
      at org.jboss.logging.Log4jService.preRegister(Log4jService.java:137)
      at com.sun.management.jmx.MBeanServerImpl.preRegisterInvoker(MBeanServerImpl.java:2245)
      at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:513)
      at javax.management.loading.MLet.getMBeansFromURL(MLet.java:523)
      at javax.management.loading.MLet.getMBeansFromURL(MLet.java:369)
      at org.jboss.Main.(Main.java:180)
      at org.jboss.Main$1.run(Main.java:110)
      at java.security.AccessController.doPrivileged(Native Method)
      at org.jboss.Main.main(Main.java:106)
      log4j:ERROR Could not instantiate appender named "Console".

      What is wrong?

        • 1. Re: Problems starting

          Do you have a version of log4j in your jre\lib\ext?
          This will confuse the JBoss classloader.

          Regards,
          Adrian

          • 2. Re: Problems starting
            vpease

            No,
            log4j.jar exists only in the jboss directory

            • 3. Re: Problems starting

              This error appears when log4j.jar
              is loaded from the System classloader.
              e.g. you've added it or whatever first loads it to
              jre/lib/ext or JBOSS_CLASSPATH

              In this case, log4j cannot see classes in
              JBOSS_HOME/lib/ext.

              log4j needs to loaded by the JBoss classloader because
              it still supports Java1 and uses Class.forName()
              to load classes.

              Regards,
              Adrian

              • 4. Re: Problems starting
                vpease

                Thank you man!!
                i set the environment variable PATH to %JAVA_HOME\BIN only and now JBoss is up and running

                • 5. Re: Problems starting
                  richardberger

                  I am having the same problem, as I am trying to use Systinet's wasp.jar. According to their instruction, this jar needs to be in the CLASSPATH, but it causes log4j to break in the manner described earlier in this thread.

                  I can't take it out, I can't have it in. Is there any way around this problem? I tried putting the .jar file in lib/ext (both from HOME and from server/default) but every time I run my simple .jsp I get "package org.idoox.webservice.client does not exist" (it is in the wasp.jar file).

                  Any help would be greatly appreciated!
                  RB