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/10/26 00:07:31 UTC

DO NOT REPLY [Bug 13983] New: - RMI call from Web Application throws SocketException if CATALINA_HOME has a space in it

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=13983>.
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=13983

RMI call from Web Application throws SocketException if CATALINA_HOME has a space in it

           Summary: RMI call from Web Application throws SocketException if
                    CATALINA_HOME has a space in it
           Product: Tomcat 4
           Version: 4.1.12
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: kuchhal@yahoo.com


We have a web application that we recently started deploying as WAR file 
(before it used to get deployed in exploded format). Our web application makes 
a RMI call to another RMI server. It seems the RMI calls works fine as long as 
CATALINA_HOME does not have any spaces in its installation path.

For example: The RMI call throws Socket Exception, Connection reset by peer if 
the Tomcat installatin directory is "C:\Tomcat 41". Just renaming the directory 
to "C:\Tomcat41" makes the application work OK. The WAR file path 
is "C:\XX.WAR".

Note that RMI call works OK if we deploy the application in exploded format 
("C:\XX\WEB-INF\*") regardless of whether there are any spaces in Tomcat 
installation path or not.

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