0 Replies Latest reply on Aug 15, 2007 10:16 AM by Paul Edwards

    Jboss, webapps, and the classloader

    Paul Edwards Newbie

      Guys,

      I have an issue. I'm running jboss 4.0.5GA. I have a war file. I'm running class isolation for the war, via jboss-web.xml:

      <jboss-web>

      <class-loading java2ClassLoadingCompliance='false'>
      <loader-repository >
      pauls.war:loader=pauls.war
      <loader-repository-config >
      java2ParentDelegaton=false
      </loader-repository-config>
      </loader-repository>
      </class-loading>
      </jboss-web>

      And thats fine, the war starts up. However if I then access the jmx functionality of my war, I get class not found exceptions. I can see that its defaulting back to the default unified classloader. Why is this? Can I stop this?

      I can fix this, by dumping all my jars out of my war into the /server/lib directory, then the unified loader finds them.

      What is the best solution? The only reason I went for class isolation originally was so that the logging didn't get conflicted.

      Thanks
      P.