We have a large server which has three main processes, JBoss (b3.2.1) and another server JVM process "jserver" which has 30 RMI interfaces and another JVM running some servlets and jsps "jservlets". (Eventually, we want to merge "jservlets" JVM into JBoss).
On the frontend we have apache webserver running at port 80.
I am trying to replace the standalone rmiregistry process with JBoss's JNDI services. I got it to work after changing the Naming.rebind() and Naming.lookup() methods to InitialContent.rebind() and InitialContext.lookup().
However, we have some Swing clients which access our RMI services through a firewall. I found that after switching to JNDI, the HTTP tunneling feature of RMI no longer worked.
Before, the RMI calls would tunnel through port 80 by calling http://server:80/cgi-bin/java-rmi.cgi on the apache webserver. (I have actually configure a servlet servlet/RMIHandler to avoid the JVM exec in java-rmi.cgi).
Is there a way to configure the JBoss JNDI and/or the clients so that the RMI can tunnel through port 80 using tha cgijava-rmi.cgi script?