tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Fowler" <>
Subject RE: RMI with the IIS/Tomcat behind a firewall
Date Sun, 18 Mar 2001 19:04:14 GMT
Take a look at the following link. It uses HTTP to connect to a servlet and
then the servlet does everything else:-

It's all pure Java.


Adam Fowler
Second year Computer Science undergraduate
University of Wales, Aberystwyth
Carroll College, WI, USA(2000-2001)
"Every new beginning comes from some other beginning's end"

-----Original Message-----
From: Sascha Richter []
Sent: Saturday, March 17, 2001 7:54 PM
Subject: RMI with the IIS/Tomcat behind a firewall


I have an IIS webserver working with tomcat behind a firewall and we
want to use RMI objects on our server. Because of the firewall we can
not conntact to port 1099 directly. It seems to exists only two
solution, the CGI script called java-rmi.cgi, which is available in the
unix distribution of the jdk and a servlet called rmiservlethandler. I
don't know how to adapted the CGI script to use it with the IIS webserver.
So a context /rmiservlethandler is created on our server and it works.
But the problem is, that RMI clients call /cgi-bin/java-rmi.cgi by
default to tunnel a firewall. The readme says, that all calls for
/cgi-bin/java-rmi.cgi should be redirected to the servlet.
A redirect within the IIS fails, because the redirects doesn't work in a
transparent manner, but by sending the client a redirect command (30X
Error), requesting  the client to reload the new url. This method seems
not to work for RMI clients.
Another method is, to map /cgi-bin/java-rmi.cgi to the ajp12 worker and
to create a new context cgi-bin under tomcat and to rename the
servletname rmiservlethandler in java-rmi.cgi. If the url
/cgi-bin/servlet/java-rmi.cgi is called, it works, but if the url
/cgi-bin/java-rmi.cgi is called, the servlet is naturally not found.
I need to call /cgi-bin/java-rmi.cgi and not
/cgi-bin/servlet/java-rmi.cgi to tunnel our firewall.
Is there a way to map a request without having the "/servlet" path
included ?
Exists other methods to tunnel a firewall ?


View raw message