-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1, JBossAS-4.0.2 Final
-
None
The Remote RMI classloading is not downloading classes that are
inside packed hot-deployed jars which are not EJB jars.
The problem is the way it is trying to construct the url is wrong, e.g.
// NOT AN EJB CLASS
2005-05-05 15:59:43,288 TRACE [org.jboss.web.WebServer] No loader, reset filePath = test/jboss/rmi/server/rmiServer_Stub.class
// TRIES TO LOAD THE BYTECODE
2005-05-05 15:59:43,288 TRACE [org.jboss.web.WebServer] loader = org.jboss.mx.loading.UnifiedClassLoader3@1632847
2005-05-05 15:59:43,288 TRACE [org.jboss.web.WebServer] loading className = test.jboss.rmi.server.rmiServer_Stub
// CORRECT
2005-05-05 15:59:43,288 TRACE [org.jboss.web.WebServer] clazzUrl = file:/home/ejort/temp/jboss-4.0.2/server/default/tmp/deploy/tmp27229testRMIServer.sar
// WRONG
2005-05-05 15:59:43,288 TRACE [org.jboss.web.WebServer] new clazzUrl: file:/home/ejort/temp/jboss-4.0.2/server/default/tmp/deploy/test/jboss/rmi/server/rmiServer_Stub.
class
2005-05-05 15:59:43,289 TRACE [org.jboss.web.WebServer] HTTP code=404 /home/ejort/temp/jboss-4.0.2/server/default/tmp/deploy/test/jboss/rmi/server/rmiServer_Stub.class
It should more like:
new clazzUrl: jar:file:/home/ejort/temp/jboss-4.0.2/server/default/tmp/deploy/tmp27229testRMIServer.sar!test/jboss/rmi/server/rmiServer_Stub.
class
- is related to
-
JBAS-1969 Look into DynLoadingUnitTestCase failure since dynclassloading change
- Closed