1 Reply Latest reply on Aug 25, 2003 5:44 AM by Markus Menner

    WAR deployment 3.2.0/Tomcat vs. 3.2.2/Tomcat

    Markus Menner Newbie

      Hi,

      there must be a difference (or bug ?) between JB 3.2.0/Tomcat and 3.2.2RC1/Tomcat concerning the classloading/deployment of WAR files.

      I have several webapps packaged in WAR's containing JAR's in the lib directory, some of them containing the same classes. I package the needed JAR's with my webapps, different WAR's can contain the same JAR's.

      As far, as I understood, this is no problem with WAR's: each one should have it's own classloader pointing to the "local" lib directory in the WAR.

      With JB 3.2.0 everything works fine, but JB 3.2.2 complains about "Duplicate classes"? Is this correct? Can I get the behavior as of 3.2.0 in 3.2.2?

      Here's the Exception thrown:

      17:47:34,440 WARN [ClassLoadingTask] Duplicate class found: net.sf.saxon.TransformerFactoryImpl
      Current CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22998testapp.war/WEB-INF/lib/saxon7.jar <no certificates>)
      Duplicate CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22973synlab.war/WEB-INF/lib/saxon7.jar <no certificates>)
      17:47:34,442 WARN [ClassLoadingTask] Duplicate class found: net.sf.saxon.TransformerFactoryImpl
      Current CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22998testapp.war/WEB-INF/lib/saxon7.jar <no certificates>)
      Duplicate CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22951krollontrack.war/WEB-INF/lib/saxon7.jar <no certificates>)
      17:47:34,442 WARN [ClassLoadingTask] Duplicate class found: net.sf.saxon.TransformerFactoryImpl
      Current CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22998testapp.war/WEB-INF/lib/saxon7.jar <no certificates>)
      Duplicate CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22948guiserver.war/WEB-INF/lib/saxon7.jar <no certificates>)
      17:47:34,509 WARN [ClassLoadingTask] Duplicate class found: net.sf.saxon.DOMDriver
      Current CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22998testapp.war/WEB-INF/lib/saxon7.jar <no certificates>)
      Duplicate CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22973synlab.war/WEB-INF/lib/saxon7.jar <no certificates>)
      17:47:34,510 WARN [ClassLoadingTask] Duplicate class found: net.sf.saxon.DOMDriver
      Current CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22998testapp.war/WEB-INF/lib/saxon7.jar <no certificates>)
      Duplicate CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22951krollontrack.war/WEB-INF/lib/saxon7.jar <no certificates>)
      17:47:34,511 WARN [ClassLoadingTask] Duplicate class found: net.sf.saxon.DOMDriver
      Current CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22998testapp.war/WEB-INF/lib/saxon7.jar <no certificates>)
      Duplicate CS: (file:/opt/jboss.322/server/all/tmp/deploy/tmp22948guiserver.war/WEB-INF/lib/saxon7.jar <no certificates>)










        • 1. Re: WAR deployment 3.2.0/Tomcat vs. 3.2.2/Tomcat
          Markus Menner Newbie

          There is still a similar isue. I tried 3.2.2RC3 today.

          With my WAR, I deploy a Web-service (with its own axis.jar). The Web-service uses a singleton.

          Upon redeployment, the same singleton instance keeps living. This was not the case with 3.2.0 and 3.2.1.

          I thought, that each WAR has a separate classloader? If this were the case, the web-service should create a new singleton instance after redeploying ...

          What changed?

          Thanx