Under Jboss/Tomcat there is an option in the tomcat4-service.xml to turn off the Java2 class loading. I.e.
<!-- Uncomment this if you want interval snapshot for the
You could try setting the attribute to false.
Best of luck.
I set Java2ClassLoadingCompliance=false and it seemed to fix the classpath problem, but it caused a bunch of other problems. The connection pools that were working before don't seem to be available in the jndi now. I tried to add a resource-ref to the web.xml and jboss-xml.xml to tie resource to the jndi name; but it then I get other timeout exceptions. So, long story short it seemed to cause more problems that it solved. Are there any other things I could try? How are the classloaders organized in jboss? I would tend to think that classes in one jar or war shouldn’t be visible in other packages.