TechNote (Archived)

JRun 4: Web Server Configuration Tool fails with JNDI ports outside 2900-3000

By default, the JRun 4 Web Server Configuration tool will only recognize JRun servers that use JNDI port values within the range of 2900 to 3000. This TechNote provides an explanation of this behavior and two methods to work around this default condition.

The JRun 4 Web Server Configuration tool is a utility that facilitates the connection of an existing web site (created by web servers such as Apache, iPlanet, IIS, etc.) to a JRun 4 server. It provides the same functionality as the JRun Connector Wizard did in previous versions of JRun, by automating all of the tasks associated with installing a native JRun connector into the web server process space.

For more information on the Web Server Configuration tool and JRun connectors, please refer to the Installing JRun and JRun Administrator's guides.

When attempting to connect a JRun server with a native web server, the Web Server Configuration tool will search for the specified JNDI port within the range of 2900-3000. To determine which JRun servers are eligible to be connected to a native web server, the Web Server Configuration tool searches for JNDI ports listed in this range. The config tool designates any JRun JNDI service running within that port range as being eligible to be connected to a native web server. Any service with JNDI port values falling outside of this range will not be recognized unless one of the following procedures is used:

1. Specify the port range that your server(s) are running in when you start the web server config tool

To modify the port range, you must specify the new range values before starting the Web Server Config tool. You do this by passing in two parameters in the command line, WSConfig.PortScanStartPort and WSConfig.PortScanCount.

WSConfig.PortScanStartPort allows you to specify the starting port range (default is 2900)
WSConfig.PortScanCount allows you to specify the number of ports to search (default is 100)
WSConfig.PortScanTimeout allows you to set the timeout (default is 10 ms.)

For example, to start the Web Server Config tool specifing a port range of 4000 - 4050, use the following command:

java -DWSConfig.PortScanStartPort =4000 -DWSConfig.PortScanCount=50 -jar wsconfig.jar

2. Change the JNDI port number for your server, so that it falls within the default range

To modify the JNDI port, edit thejndi.properties file in the {jrun-server.rootdir}/SERVER-INF directory. The following is an example of setting the JNDI port within the jndi.properties file to port 2909:

 java.naming.factory.initial=jrun.naming.JRunContextFactory # # This is the JNDI listen port.  Any port number is okay, but # the webserver connector installer will auto-discover the port # if you use a value between 2900-3000 #java.naming.provider.url=localhost:2909 java.naming.factory.url.pkgs=jrun.naming jrun.naming.rebind.enable=false jrun.naming.bind.enable=true jrun.naming.rmi.port=0 #java.naming.rmi.serverSocketFactory=jrunx.net.SSLServerSocketFactory #java.naming.rmi.socketFactory=jrunx.net.SSLSocketFactory jrun.naming.orb.enable=false jrun.naming.orb.host=localhost jrun.naming.orb.port=900 jrun.naming.file.enable=false

After modifying the JDNI port (by settingjava.naming.provider.url=localhost:2909 in the above example), restart the JRun server to force the change to take effect. As long as the JNDI port is between 2900-3000, the web server config tool will recgonize the JRun server and allow it to be configured with a native web server.