9 Replies Latest reply on May 27, 2008 12:40 PM by japuentem

    "org.jboss.logging.util.OnlyOnceErrorHandler" object is not

    sramired

      Hello
      I am seeing exception when Jboss4.0.2 startsup. Looks like this issue is related to Logging, but after this my .war gets loaded properly and logging is working.
      Kindly let me know if this is something to be fixed.

      13:46:32,556 INFO [STDOUT] log4j:ERROR A "org.jboss.logging.util.OnlyOnceErrorH
      andler" object is not assignable to a "org.apache.log4j.spi.ErrorHandler" variab
      le.
      13:46:32,576 INFO [STDOUT] log4j:ERROR The class "org.apache.log4j.spi.ErrorHan
      dler" was loaded by
      13:46:32,586 INFO [STDOUT] log4j:ERROR [WebappClassLoader
      delegate: false
      repositories:
      /WEB-INF/classes/
      ----------> Parent Classloader:
      java.net.FactoryURLClassLoader@cb6a34
      ] whereas object of type
      13:46:32,616 INFO [STDOUT] log4j:ERROR "org.jboss.logging.util.OnlyOnceErrorHan
      dler" was loaded by [org.jboss.system.server.NoAnnotationURLClassLoader@f62373].

      13:46:32,806 INFO [STDOUT] log4j:ERROR Could not create an Appender. Reported e
      rror follows.
      13:46:32,816 INFO [STDOUT] java.lang.ClassCastException
      13:46:32,826 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.parseApp
      ender(DOMConfigurator.java:165)
      13:46:32,836 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.findAppe
      nderByName(DOMConfigurator.java:140)
      13:46:32,846 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.findAppe
      nderByReference(DOMConfigurator.java:153)
      13:46:32,856 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.parseChi
      ldrenOfLoggerElement(DOMConfigurator.java:415)
      13:46:32,876 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.parseRoo
      t(DOMConfigurator.java:384)
      13:46:32,886 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.parse(DO
      MConfigurator.java:790)
      13:46:32,896 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.doConfig
      ure(DOMConfigurator.java:673)
      13:46:32,906 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.doConfig
      ure(DOMConfigurator.java:616)
      13:46:32,916 INFO [STDOUT] at org.apache.log4j.xml.DOMConfigurator.doConfig
      ure(DOMConfigurator.java:602)
      13:46:32,926 INFO [STDOUT] at org.apache.log4j.helpers.OptionConverter.sele
      ctAndConfigure(OptionConverter.java:460)
      13:46:32,936 INFO [STDOUT] at org.apache.log4j.LogManager.(LogManag
      er.java:113)
      13:46:32,946 INFO [STDOUT] at org.apache.log4j.Category.getRoot(Category.ja
      va:595)

      Thanks

        • 1. Re:
          gabehamilton

          I believe I had the same problem, the behavior of the class loader changed in 4.0.2.

          At the bottom of JBAS-1691 is a solution: switch back to the old behavior by changing jboss-service.xml.

          http://jira.jboss.com/jira/browse/JBAS-1691


          Comment by Adrian Brock [03/May/05 07:40 PM]

          To revert to pre-4.0.2 config use:
          <attribute name="Java2ClassLoadingCompliance">true</attribute>
          <attribute name="UseJBossWebLoader">true</attribute>
          





          • 2. Re:
            sandello

            I tried all combination of

            <attribute name="Java2ClassLoadingCompliance">true</attribute>
            

            <attribute name="UseJBossWebLoader">true</attribute>
            

            <attribute name="Java2ClassLoadingCompliance">false</attribute>
            

            <attribute name="UseJBossWebLoader">false</attribute>
            

            and in all case I got different errors. What I did whong?

            • 3. Re:
              sandello

              I use JBoss 4.0.3sp1

              • 4. Re:
                sandello

                Problem solved: I removed log4j.jar from app.wap:/WEB-INF/lib

                • 5. Re:
                  prohgy

                  Very good, Sandello. I had this problem, I removed log4j.jar from my application on Jboss and it startup without problem.

                  • 6. Re:
                    binodkumarsuman

                    Nice, very nice. Simply I removed all the Log4j*.* from WEB-INF\lib of all the application inside the deploy folder. It is working fine.
                    Thanks.

                    • 7. Re:
                      mvsntakesh

                      I too had simmilar problem......Is there any way without removing log4j.jar coz i am using it in my application.....

                      • 8. Re:
                        jaikiran

                         

                        "mvsntakesh" wrote:
                        I too had simmilar problem......Is there any way without removing log4j.jar coz i am using it in my application.....


                        Which version of JBoss? For JBoss-4.2.x, have a look at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125552

                        • 9. Re: I have a question
                          japuentem

                          i remove log4j.jar but jboss don't need the jar file for any other operation?