You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Dan Powell <Da...@Wellogic.com> on 2001/10/01 21:32:03 UTC
Tomcat 4 and rmiregistry
When starting rmiregistry from within Tomcat 4 I am unable to bind to
anything from my web applications. rmiregistry starts just fine, but I
just can't bind. This is only a problem if I install Tomcat 4 to a
directory with spaces in the path. If I move my Tomcat 4 installation
to a "simpler" directory, all is well. If I try Tomcat 3.2.3 everything
works fine regardless of spaces in the pathname. This problem seems to
be related to the classloader, although I'm having trouble tracking it
down further at this time. Has anyone experienced similar problems or
is able to point me in a direction that could help?
Thanks,
--
J. Daniel Powell
Sr. Systems Architect
Wellogic, Inc.