3 Replies Latest reply on Oct 25, 2007 10:16 AM by vamsi77

    problem with jboss 4.2 and log4j

      Hi all,

      I'm facing to a problem withe jboss 4.2 and log4j.
      My application works correctly with jboss 4.3 sp1. But when I deploy it to jboss 4.2, The server complain againts log4j.
      It seems to me that there is a classloading problem.
      Here is the stack trace:


      log4j:ERROR A "org.jboss.logging.appender.FileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
      log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
      log4j:ERROR [WebappClassLoader
      delegate: false
      repositories:
      /WEB-INF/classes/
      ----------> Parent Classloader:
      java.net.FactoryURLClassLoader@11da1f8


      If someone can help.
      thank in advance.
      Meissa

        • 1. Re: problem with jboss 4.2 and log4j
          mottersb

          Hi Meissa,

          we have the same problem!
          We found this helpful: http://www.openrdf.org/forum/mvnforum/viewthread?thread=1296

          but does not actually resolve the problem.

          The suggestion is to remove our copy of log4j1.2.8 library from our application, but this is not right as the application has been tested against this library.

          cheers,

          Marc

          • 2. Re: problem with jboss 4.2 and log4j

            It sound like jboss classloading nightmare is back again.
            In jboss 4.0.3sp1 all of our application was working fine.
            With 4.0.5 version, we had to deal with classloading isolation to to be able to use log4j.
            And now, we have to remove log4j in to make ous application dependent to jboss log4j version.
            I wonder if jboss guys are measuring the negative impact thoses changes bring to those who want to migrate.
            It's becomming more and more painful to migrate from a version to another.
            There is nowhere in the doc to find thoses changes.
            So I'd like to say to jboss guys to please be as professionnal as they claim
            while making new versions.


            Meissa

            • 3. Re: problem with jboss 4.2 and log4j

              Did u able to solve it?