2 Replies Latest reply on Nov 11, 2011 1:51 AM by jaikiran

    JBoss 5.1 bleeding Wars

    gboro54

      We have two wars deployed on the same server, which happen to have a class named the same(say class A). After running for a while, Springs reflection seems to pick up the other war's class and try to perform an operation on that class. We have added the following to both wars but can't see to prevent it from occuring. Are we missing something?

       

       

      The following snippets from jboss-classloading.xml(placed in the web-inf directory).

       

       

      {code:xml}

      <classloading xmlns="urn:jboss:classloading:1.0"

      name="a.war"

      domain="a.war"

      export-all="NON_EMPTY"

      import-all="false"

      parent-first="false">

      </classloading>

       

       

      <classloading xmlns="urn:jboss:classloading:1.0"

      name="b.war"

      domain="b.war"

      export-all="NON_EMPTY"

      import-all="false"

      parent-first="false">

      </classloading>

      {code}

       

        • 1. Re: JBoss 5.1 bleeding Wars
          gboro54

          No clues to preventing this or what is wrong with the jboss-classloading.xml above?

          • 2. Re: JBoss 5.1 bleeding Wars
            jaikiran

            Which version of JBoss AS? You don't need those config files since .war deployments are isolated by default (as mandated by spec). Is this a clean JBoss installation? Also can you post the relevant details which show that the class from the other war is being picked up?