You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/03/22 11:08:45 UTC

DO NOT REPLY [Bug 7359] New: - Classloader problems with RMI

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7359>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7359

Classloader problems with RMI

           Summary: Classloader problems with RMI
           Product: Tomcat 4
           Version: 4.0.3 Final
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: per.edlund@bozoka.com


Here's the problem:

A servlet uses Jini to locate a jini service (which is an RMI server). When found, downloading that services stub starts. When this occures, a NoClassDefFound is generated. The RMI server has a codebase server which delivers jar files from a codebase server (web server). 

THE BUG: If the codebase is set to file:/home/per/dev/ior/lib/service-dl.jar everything works fine and the servlet finds the classes in the service-dl.jar. On the otherhand, which is the correct way, the codebase is set to http://192.168.x.x:8585/service-dl.jar the class is not found.

There is no doubt that the codebase is up and delivers this jar, since it is used from other clients as well. This is the reason I beleve that this is a bug in tomcat.

Please give me a hint quickly on this matter, since I'm depending on this

/P

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>