The C portion of Apache JServ was not able to automatically startup the Java portion of Apache JServ.

The reason why this happens is generally due to a misconfiguration of the jserv.properties file or you are on Windows and you have a ApacheJServ.jar file of zero length (or the .jar file is corrupted for some reason).

If you have the zero length .jar file, read the directions on http://java.apache.org/jserv/dist/ that are in bold red letters.

If you do not have the zero length .jar file problem, then what you need to do is make sure that your jserv.properties file is 100% correct. Here are a few common misconfigurations:

#1. You have an empty wrapper.classpath= line. Make sure that wrapper.classpath= has the path to the JSDK 2.0 .jar file and the ApacheJServ.jar file. You should have no empty wrapper.classpath= lines.

#2. The paths to your zone properties files are incorrect. These should be full absolute paths to the files.

#3. If you have log.true= and the JVM process id (generally this is the same id as the httpd server runs as) cannot write to the file defined in log.file=. This could be because you have not defined the log.file= line correctly. If you see a log.file=@JSERV_LOG@/jserv.log line in your jserv.properties file, you should make sure that you set the log.file= to point to a valid jserv.log file on your hard disk.