Please browse the categories below to previous answers to questions like yours. If you do not find the answer for your particular situation, ask for help on the appropriate mailing list.
(Answer) (Category) Java Apache Project : (Category) Apache JServ 1.0 : (Category) Configuration :
When accessing any servlet I get the following error: "Premature end of script headers".
Take the :8007 out of the url you are trying to use. You are connecting to the servlet engine running on port 8007, not your webserver which is probably running on port 80.
Chances are that the JVM has not started up properly. About the only time that the JVM will not startup properly is if you have a mis-configuration in your httpd.conf or jserv.properties, or [zone].properties files. You need to properly setup the configuration directives in these files before the JVM will startup properly.

Apache JServ is two parts. A C portion which is mod_jserv.c and is either compiled into Apache or loaded in as a DSO. The other part is a Java Application that has no GUI interface, just a main() method that starts up and listens on a port. The C portion talks to the Java portion via network sockets. If the C portion is not able to correctly communicate with the Java portion (generally due to a misconfiguration on your part), then you will receive "Premature end of script headers" errors.

I was having a similar problem. every time I attempted to access a servlet, the VM crashed and I recieved these messages in the error log:
[07/06/1999 15:12:34:543] (ERROR) an error returned handling request via protocol "ajpv11" [07/06/1999 15:12:53:420] (EMERGENCY) ajp11: cannot scan servlet headers
I was running the JDK1.1.6 VM, I switch the the 1.2.1 VM and everything is fine...
We've also been having this problem. However, the JVM seems to run fine for small servlets; the distribution Hello.class servlet runs fine. We tried upgrading to the latest 1.2 JVM--no luck.
dkingATopentableDOTcom
About the JDK1.1.6 issue: java.exe crashes always on Windows NT SP4 when starting JServ, at least mine does (JVM bug?)

With JDK1.2.1 we also had this "small servlets run fine but big ones don't"-problem.
This happens only when JServ starts automatically with Apache, but if JServ is started manually it works. This is how to do it:
-Tell JServ to start manually in mod_jserv.conf change "ApJServManual on"
-Start apache (mine is NT-service and works fine, don't know about console)
-Start JServ in a command prompt:
java org.apache.jserv.JServ \conf\jserv.properties
This should work.

I haven't figured out what's wrong with the automatic start in my case, any ideas?
nurminenATgordionDOTcom

I get the same error. I send a POST request to the servlet. When I send the request from my network which is after a transparent HTTP proxy. If I send it from outside it's okay. I call it bad luck !!
georgeATsibnetDOTro
I got this error when my servlet could not find the applet( I changed packages). Check the access_log and jserv.log (or whatever it's called on your site). It could be that the repository was missing or the jar-file is nowhere to be found (in .properties)
AndreasDOTKutscheraATblnDOTsiemensDOTde
I've had the same problem: the JVM crashes on Windows NT when starting JServ, even when started manually, as nurminenATgordionDOTcom proposed. I solved the problem by disabling the jit-Compiler:
in jserv.properties: wrapper.bin.parameters=-nojit
(-nojit is the required parameter to disable the jit-Compiler for Sun's JVM 1.1.6 on Win32-Systems)
tDOTvahrstATgmxDOTde
I had the "Premature end of script headers" error also. I fixed the problem by changing the APJServMount configuration from
APJServMount /servlets /root
to
APJServMount /servlets ajpv11://localhost:8007/root

marcusATmkazDOTcom
[Append to This Answer]
Previous: (Answer) How do I setup basic authentication with Apache and Apache JServ?
Next: (Answer) What other documentation for configuration is available?
This document is: http://java.apache.org/faq/?file=28
[Search] [Appearance] [Show Expert Edit Commands]
This is a Faq-O-Matic 2.709.
Please browse the categories below to previous answers to questions like yours. If you do not find the answer for your particular situation, ask for help on the appropriate mailing list.