4 Replies Latest reply on May 9, 2005 12:47 PM by starksm64

    JBoss 4.0.1sp1 to 4.0.2 upgrade problem

    javaspack

      I thought this would be a simple upgrade. Download the zip, extract it, change my log4j.xml and jboss-service.xml files, deploy my app, and it doesn't work.

      Here's my specs:
      Windows XP
      Java 1.5.0_02


      I still have 4.0.1sp1 installed and it works with the exact same deployment. However, with 4.0.2 I'm now getting the following error in the tomcat deployer:

      INFO [WebappClassLoader] validateJarFile(C:\dev\rmbm\build\server\rmbm.ear\rmbm-web.war\WEB-INF\lib\j2ee.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
      INFO [STDOUT] log4j:ERROR A "org.jboss.logging.appender.FileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
      INFO [STDOUT] log4j:ERROR Could not instantiate appender named "FILE".

      It doesn't seem like anything major, but the app starts throwing all sorts of EJB exceptions after that.

      I've tried replacing the j2ee.jar with the latest from Sun.
      I've tried replacing my log4j.jar files with the one that comes in 4.0.2.
      I've looked at different Tomcat settings, since the version has gone from 5.0 to 5.5, but nothing seems to help.

      Some sort of .jar collision? Anybody else seeing this?

        • 1. Re: JBoss 4.0.1sp1 to 4.0.2 upgrade problem
          starksm64

          There should never be a j2ee.jar in the war in any app server. This has to be provided by the app server. Read the release notes for the class loading config change.

          • 2. Re: JBoss 4.0.1sp1 to 4.0.2 upgrade problem
            grafpoo

            i've had the same error message about the appender, but it came about because i have log4j1.2.8.jar in my war file. when i remove it from the war file, all is well.

            but i don't want to remove it from the war-file; i want to try to keep my war deploy app-server-agnostic.

            i've just looked at the release notes, which point me to JBAS-1691, which says i can restore old behavior by setting a couple of attributes (Java2ClassLoadingCompliance and UseJBossWebLoader), but i'd prefer having an out-of-the-box jboss work with my war (with log4j).

            willing to admit i've fudged this ... john

            • 3. Re: JBoss 4.0.1sp1 to 4.0.2 upgrade problem
              grafpoo

              by the way, i am running java 1.5_03...

              • 4. Re: JBoss 4.0.1sp1 to 4.0.2 upgrade problem
                starksm64

                When a deployment includes classes used by the implementation of the app server, you don't have an app server agnostic deployment by definition. Either the class loading configuration of the app server needs to be configured to work with your packaging, or the packaging updated to work with the default app server configuration.