What does this error mean?
Could not connect to JRun Connector Proxy. Please contact the system adminstrator for this web site.
Web Servers communicate to JRun via a socket-based protocol called the JRun Connector Proxy (JCP for short). If the web server cannot connect to JRun, it issues this error. Typically this is caused by one of following two reasons:
- JRun hasn't been started
- The JCP port JRun is listening on isn't the same as the port the web server connector plugin is using.
In the first case, you simply need to start JRun. In the second, you will need find out what port JRun is listening on and make sure that is the port the connector is using. You can determine this port by examining the event.log file after starting JRun. Look for the line that looks like this:
[Tue Jul 06 13:31:28 PDT 1999] JRun Connector Proxy Started on port 8081.
To determine what port your web server is using you need to examine the proper configuration file.
For IIS, you need to examine the jrun.ini file in the directory you chose for the IIS "scripts" directory. Typically this is C:\Inetpub\scripts. The port is stored in the "proxyport" property.
For NES, you need to examine your web servers obj.conf file. Do a search for "proxyport".
For Apache, you need to examine the httpd.conf file (apache.conf on Mac OS X). Near the bottom you'll see a line like this:
JRunConfig ProxyPort 8081
If the port settings all look correct, you may also need to change the proxy host property. If JRun is installed on the same machine as your web server, this should be "127.0.0.1". This is the IP address any machine can use to refer to itself (also known as the loopback interface). Sometimes the loopback interface on a machine isn't setup properly, in which case you can substitute the machines real IP address.
Keywords:
tn_17333
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
