Java Apache Project : Apache JServ 1.0 : Configuration :
(EMERGENCY) ajp11: can not connect to host 127.0.0.1:8007, (ERROR) an error returned handling request via protocol "ajpv11"
---------- From: "jon *" jon@clearink.com To: Java Apache Users java-apache-users@list.working-dogs.com Date: Fri, Jun 11, 1999, 11:27 AM > In the mod_jserv.log file, I get : > (EMERGENCY) ajp11: can not connect to host 127.0.0.1:8007 > (EMERGENCY) ajp11: connection fail > (ERROR) an error returned handling request via protocol "ajpv11" That error that you are getting is a result of the JVM not being able to start up properly. The error is the mod_jserv C portion of Apache JServ not being able to connect to the running Servlet Engine java portion of the process. So, you need to figure out why the JVM is not starting up properly. Make sure that all of your paths in all of your configuration files are correct. On Win32 machines, this could mean that it is an issue of having spaces in your paths. Try setting things up so that there are no spaces anywhere in any of your paths. Make sure that the path to the JVM binary executable is correct in your jserv.properties file. Make sure that your wrapper.classpath has the correct paths to the JSDK and the ApacheJServ.jar file. Make sure that your permissions are set properly on your log files so that the userid that the httpd runs under can write to them. -jon
Unless the jserv.log file is happy, the jserv engine will throw an error and write out a stack trace to the error.log.
In my case the problem that stopped the jserv engine from starting was a problem with the name/access of the jserv.log file. Even though the log file seems to be specified in both the jserv.properties and the jserv.conf files, the one that appears to be important to the start up is the one in jserv.properties.
In httpd.conf, make sure you've put the proper hostname for ApJServDefaultHost! If Apache, etc. are configured for a hostname other than "localhost", you've got to make sure JServ can find the same host.
(This cost me almost two days.)
# Set the name of the trace/log file. To avoid possible confusion about # the location of this file, an absolute pathname is recommended. # On Unix, this file must have write permissions by the owner of the JVM # process. In other words, if you are running Apache JServ in manual mode # and Apache is running as user nobody, then the file must have its # permissions set so that that user can write to it. # Syntax: log.file=<log file name> (String) # Default: NONE log.file=/you/must/use/a/full/path/and/it/tells/you/jserv.log
Many thanks to this FAQ for getting me going in the right direction.
This caused both jserv.properties:wrapper.bin to be set to /usr/java and the JAVA variable in all the jserv Makefiles, most notably, the example/Makefile, to be misconfigured. All makefiles need JAVA set to /usr/bin/java (or wherever your java executable is), likewise with the jserv.properties:wrapper.bin
If you do have to make that change, you will have to re-make both jserv and Hello. To re-make Hello, go to the example direcotry, fix the JAVA variable, make clean (to remove the old copy), and make. It would probably be a good idea to re-make all of jserv, but just remaking Hello got me past the (EMERGENCY) error.
-David Schlussel dschluss@slip.net
using blackdown java (1.2pre2) and apache 1.3.6, i found it necessary to set wrapper.classpath=/path/to/java/jre/lib/rt.jar (in addition to) wrapper.classpath=/path/to/jserv/lib/ApacheJServ.jar wrapper.classpath=/path/to/jsdk/lib/jsdk.jar in the servlet.properties file. w/o the classpath to rt.jar, the thing blows up everytime.
I've got similar error, on my machine which is using SunOS 5.6 (Solaris 2.6 ). I was using jdk1.2.1 and was getting this message in my error_log : ---------- You must install a Solaris patch to run this version of the Java runtime. Please see the README and release notes for more information. Exiting. ---------- When I switch from jdk1.2.1 to 1.1.6 everything worked fine.
If you do specify a "log.file" & make sure it is writable by the running process, the org.apache.jserv.JServ will not be able to start up and will not be listening on 8007 for requests. There will be little or no indication of this state of affairs in the log file, so be careful! Hint: the first error you will get in this situation is "(EMERGENCY) ajp11: can not connect to host 127.0.0.1:8007" when you try to hit a servlet.
I have tried all things mention here but I still got ajp11: cannot connect ot host 127.0.0.1:8007 Breifly: my jserv.log is owned by nobody. I can su to nobody and run jserv manually. all classpath and path are correct. What's wrong here. This is my platform: Redhat 6.0 with Linux kernel 2.2.5 Apache 1.3.9 and Jserv 1.0 Sunsoft JSDK 2.0
1. The complete-path(!) name to the log-file must be the same in jserv.log and jserv.properties,
and the file must be writeable. I changed mode to 777, perhaps this was too much.2. security.allowedAddresses had to be the real name (not localhost or 127.0.0.0)
After these changes JServ started.
# Attach the loopback device and add route /sbin/ifconfig lo 127.0.0.1 /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
lyonbfATornlDOTgov
After some try-error, i've put "ApJServLogLevel debug" in jserv.conf , after
that in mod_jserv.log appears:
..... [18/10/1999 22:41:03:011] (INFO) wrapper: Java VM died 5 times in a row with
less than 120 seconds between successive failures, setting delay to 60 seconds
before restarting. Check the Apache error log and the Apache JServ
log files for more details; for maximum log information be sure to
enable the Apache JServ log file in the main jserv properties file by: setting
the 'log' property to true, the 'log.file' property to a file
writable by the uid as whom Apache JServ is run, and by enabling log channels
using the 'log.channel.*' properties)
[18/10/1999 22:41:51:170] (INFO) wrapper: Java VM restarting (PID=5177)
[18/10/1999 22:41:51:172] (INFO) wrapper: Java VM spawned (PID=5215, PPID=5177)
[18/10/1999 22:41:51:174] (INFO) wrapper: Java Virtual Machine unable to start (ERR=2: No such file or directory)
[18/10/1999 22:41:51:174] (ERROR) wrapper: printing debugging information (command line, env)
.....
The message :(ERR=2: No such file or directory)
reminds me to check the executable java path. On rh-6.0 it's /usr/bin/java & not /usr/local/java/bin/java as in the default installed files.
After changing the java executable path in jserv.properties, all OK!
tronyATlaofficesDOTcom
I continually received this error until
I changed the version of the JSDK I using.
Good luck.
deepaksharma_98ATyahooDOTcom
Environment Variables