IDependOn-Set: 1
IDependOn-Set: 2
IDependOn-Set: 286
IDependOn-Set: 287
IDependOn-Set: 298
IDependOn-Set: 7
LastModifiedSecs: 939408348
Parent: 7
SequenceNumber: 7
Title: (EMERGENCY) ajp12: ping: no reply
Part: 0
Author-Set: jon@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 939408348
Type: 
Lines: 41
Ok,

You will get this error for a few reasons. Unfortunately, most of which can be hard to debug. I'm going to do a really good job pointing you to the reasons the error occurs and what you might be able to do about it, although, you WILL have to debug this on your own so don't go crying on the java-apache-users mailing list about this problem.


Reason Number 1

---------------


There are two parts to Apache JServ. A C portion and a Java portion. For most configurations, when Apache starts up, the C portion (mod_jserv) attempts to also start up the Java portion (the JVM). The C portion communicatates with the Java portion via a protocol called ajpv12. If the C portion is not able to start up the Java portion and then "ping" it, then you will get this error. Essentially, what is happening is that the Java portion just won't start up. This is 99% of the time due to a configuration or setup error on your part.


The first thing to do is to make 100% sure that all the paths in all your configuration files are correct. If anything is wrong, the Java portion will not start.


The next thing to do is to make 100% sure that your log files, there are TWO of them, can be written to by the process that the httpd is running as (generally this is "nobody"). chown the files to be owned by nobody or make them writtable by everybody. If Apache JServ cannot write to these files, then nothing will be logged and you will be at a loss. We can't show you any errors because we don't ahve permissions to!


If you think that you have all of the above correct AND you are still getting this error, GO BACK AND CHECK AGAIN!!!!!


Reason Number 2

---------------

Ok, so you have gone back and checked a million times and you are still getting this error. Chances are that you are upgrading from Apache JServ 1.0 and you are still pointing at the OLD ApacheJServ.jar file. Well, I just caught you lying to yourself and you didn't actually check all your paths because you obviously are still using an old file. Duh. Smack your head on the wall. Did I mention that this is well documented in the upgrade.html file in the docs directory.


Reason Number 3

---------------

Try increasing the value for ApJServVMTimeout in the jserv.conf file. This setting is the amount of time (in seconds) that the C portion gives the Java portion to start up. On a busy or slow system, this can take longer than the default 10 seconds.


Reason Number 4

---------------

At this point, your system should work but it isn't. Your paths are setup correctly and you have read all the entries in this stupid FAQ-O-Matic and you are still at a loss. Well, at this point, it works for everybody else on the entire planet except you. So, go out and shoot yourself because we are at a complete loss as to why it works for everone except you.
EndPart: 0
